Bind 9 Reverse Lookup

[Barry Margolin]

In article <93l06q$j42 at pub3.rc.vix.com>,
Ruben I Safir - Brooklyn Linux Solutions CEO  <ruben at mrbrklyn.com> wrote:
>
>
>
>> 
>> I do.  The server responded to reverse lookup with an NXDOMAIN answer,
>> meaning that it can't find a PTR record for its own address.
>
>OK I see. There is a message about NXDOMAIN in the logs when it
>starts up.  I thought the message related to that.
>
>>  Don't you see
>> that right after the first "Got answer:" line?
>> 
>> I did an AXFR of the zone, and I saw the following record:
>
>OK How did you do that?  

dig -x 216.112.229 axfr @216.112.229.114

>dig @mail.rm0cpa.com mail.rm-cpa.com axfer
>
>;; ANSWER SECTION:
>mail.rm-cpa.com.        86400   IN      A       216.112.229.114

That's the forward domain, which is totally irrelevant to this discussion
about reverse DNS.

>The output from this is see the dot quad without a dot on the end.  Thats
>not exactly what you discovered.  I seem to be missing an understanding on
>how the querry is called in dig to do reverse resolution.

dig -x 216.112.229.114 ptr @mail.rm-cpa.com

or

dig 114.229.112.216.in-addr.arpa ptr @mail.rm-cpa.com

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.