RFC 2317 reverse DNS - have I done it right?

[David Botham]

bind-users-bounce at isc.org wrote on 02/12/2004 05:11:29 AM:
[clip...]
> %dig -x 81.187.228.196
> 
> ; <<>> DiG 9.2.1 <<>> -x 81.187.228.196
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34887
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;196.228.187.81.in-addr.arpa.   IN      PTR
> 
> ;; ANSWER SECTION:
> 196.228.187.81.in-addr.arpa. 3600 IN    CNAME 
> 196.192-223.228.187.81.in-addr.arpa.
> 196.192-223.228.187.81.in-addr.arpa. 3600 IN PTR mx1.pandasys.net.
> 
> ;; AUTHORITY SECTION:
> 192-223.228.187.81.in-addr.arpa. 3600 IN NS     ns0.gradwell.com.
> 192-223.228.187.81.in-addr.arpa. 3600 IN NS     ns1.pandasys.net.
> 
> ;; Query time: 351 msec
> ;; SERVER: 10.69.0.1#53(10.69.0.1)
> ;; WHEN: Thu Feb 12 09:52:24 2004
> ;; MSG SIZE  rcvd: 149
> 
> So the reverse lookup is working ok, but have I done something wrong?


Perhaps your troubleshooting flow chart is missing a crucial step after 
the question "does it work?", that step is "stop" <dws> :) :)


Everything looks fine here...

Dave...


[clip...]
> 
> Thanks for any advice,
> Peter
>