Does dynamic update automatically add PTR reocrds?
Answered Wed, 1 May 2002> In my domain I would like to use dynamic update to control my zone updates.
> However I have been unable to get my name server to resolve the reverse
> lookup after an nsupdate. Below is what I have done so far am I doing
> something wrong?
>
> host@mydomain:/usr/local> nsupdate
> > prereq nxdomain newhost.mydomain.com.
> > update add newhost.mydomain.com. 300 A 192.168.0.145
> >
> > quit
> host@mydomain:/usr/local> nslookup newhost.mydomain.com
> Note: nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead. Run nslookup with
> the `-sil[ent]' option to prevent this message from appearing.
> Server: 192.168.0.1
> Address: 192.168.0.1#53
>
> Name: newhost.mydomain.com
> Address: 192.168.0.145
>
> host@mydomain:/usr/local> nslookup 192.168.0.145
> Note: nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead. Run nslookup with
> the `-sil[ent]' option to prevent this message from appearing.
> Server: 192.168.0.1
> Address: 192.168.0.1#53
>
> ** server can't find 145.0.168.192.in-addr.arpa: NXDOMA
You need to explicitly add a PTR record reverse mapping the host's IP
address back to its domain name. For example:
% nsupdate
> update add 145.0.168.192.in-addr.arpa 300 PTR newhost.mydomain.com
> send
> quit
cricket