Bind 9 Reverse Lookup
Barry Margolin
barmar at genuity.net
Thu Jan 11 18:28:56 UTC 2001
In article <93kkkb$f0k at pub3.rc.vix.com>,
Ruben I Safir - Brooklyn Linux Solutions CEO <ruben at mrbrklyn.com> wrote:
>
>
>
> - This is the output from nslookup -d
>
>I don't see anything to cuase the server not to be seen
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. 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:
114.229.112.216.in-addr.arpa IN PTR mail.rm-cpa.com.
Notice the missing "." after "arpa". Since the name doesn't end in ".",
it's not fully qualified, so the $ORIGIN is appended. Thus, the above
record is equivalent to:
114.229.112.216.in-addr.arpa.229.112.216.in-addr.arpa. IN PTR mail.rm-cpa.com.
>On Thu, 11 Jan 2001 10:38:41 Ruben I Safir wrote:
>nslookup mail.rm-cpa.com
>
>
>;; res_nmkquery(QUERY, 114.229.112.216.in-addr.arpa, IN, PTR)
>------------
>Got answer:
> HEADER:
> opcode = QUERY, id = 16909, rcode = NXDOMAIN
> header flags: response, auth. answer, want recursion, recursion
>avail., authentic data
> questions = 1, answers = 0, authority records = 1, additional = 0
>
> QUESTIONS:
> 114.229.112.216.in-addr.arpa, type = PTR, class = IN
> AUTHORITY RECORDS:
> -> 229.112.216.in-addr.arpa
> ttl = 86400 (1D)
> origin = mail.rm-cpa.com
> mail addr = root.rm-cpa.com
> serial = 5
> refresh = 43200 (12H)
> retry = 3600 (1H)
> expire = 2419200 (4W)
> minimum ttl = 86400 (1D)
--
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.
More information about the bind-users
mailing list