[comp.protocols.tcp-ip.domains] No inverse mapping question

system@asuvax.asu.edu (Marc Lesure) (09/12/90)

With all this talk about inverse mapping, I have a question about my
domain.  Our primary and secondary name servers do the proper inverse
mapping and can connect to remote machines which require the inverse map.
However, other local machines which do not run 'named' but have 
'resolv.conf' set up to use the name servers are unable to connect to
remote machines which require inverse mapping.  What needs to be done
to get inverse mapping for these other local machines?

-----------------------------------------------------------------------
Marc Lesure / Arizona State University / Tempe, AZ
"Between the world of men and make-believe, I can be found..."
"False faces and meaningless chases, I travel alone..."
"And where do you go when you come to the end of your dream?"

UUCP:       ...!ncar!noao!asuvax!lesure  
Internet:   lesure@asuvax.eas.asu.edu

cricket@hpcc01.HP.COM (Cricket Liu) (09/13/90)

    With all this talk about inverse mapping, I have a question about my
    domain.  Our primary and secondary name servers do the proper inverse
    mapping and can connect to remote machines which require the inverse
    map.  However, other local machines which do not run 'named' but have
    'resolv.conf' set up to use the name servers are unable to connect to
    remote machines which require inverse mapping.  What needs to be done
    to get inverse mapping for these other local machines?

Marc,

Looks to me like you never got the NIC to delegate authority for
219.129.in-addr.arpa to you and your nameservers.  Your nameservers all
seem to have PTR information for your hosts (good for you!), but my
nameservers can't get to you because there are no NS records pointing
authority for your class B, 129.219, to those nameservers.

Give the NIC a ring up (hostmaster@nic.ddn.mil) and give them a list of the
nameservers responsible for 219.129.in-addr.arpa and their corresponding IP
addresses.  They'll set up the NS records necessary, and anybody on the
Internet will be able to map your IP addresses back to your hostnames.

As for the inverse mapping working for your nameserver hosts, I expect that
the NIC maintains PTR records themselves for what they know of in
in-addr.arpa space that isn't delegated to someone else.

cricket

hostmaster@hp.com