Resolver Question
Kevin Darcy
kcd at daimlerchrysler.com
Fri Aug 25 00:57:11 UTC 2000
Offhand, I'd say nslookup is getting confused by the fact that multiple PTR's
exist for 2.228.214.206.in-addr.arpa.
Get rid of the extraneous PTR and use a real lookup tool like "dig".
- Kevin
Michael wrote:
> My DNS seems to be operating correctly. The operative word there
> being seems. I am no BIND wizard.
>
> I get the following output when I access my name server to lookup
> the name of the name server (or any other name) debug is set in
> the resolver.
>
> COuld someone enlighten me as to the meaning of the first few
> lines of the output from nslookup?
>
> internal.net is a ficticious name for the internal domain.
> The external domain is urbanna.net (and a couple of others).
>
> Changing this file seems to have no effect I still get the
> error on the first nameserver listed in the file.
>
> /etc/resolv.conf contains:
> domain internal.net
> search internal.net
> nameserver 206.214.228.101
> nameserver 206.214.228.2
> nameserver 206.214.228.45
> options debug
>
> The command was $>nslookup vast.urbanna.net. It produced the following
> output. This first line makes no sense to me. Help.
>
> *** Can't find server name for address 206.214.228.101: No information
>
> ;; res_setoptions(" debug
> ", "conf")..
> ;; debug
> ;; res_nmkquery(QUERY, 101.228.214.206.in-addr.arpa, IN, PTR)
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 51920, rcode = NOERROR
> header flags: response, auth. answer, want recursion, recursion avail.
> questions = 1, answers = 0, authority records = 1, additional = 0
>
> QUESTIONS:
> 101.228.214.206.in-addr.arpa, type = PTR, class = IN
> AUTHORITY RECORDS:
> -> 101.228.214.206.in-addr.arpa
> ttl = 86400 (1D)
> origin = vast.urbanna.net
> mail addr = root.urbanna.net
> serial = 20000824
> refresh = 10800 (3H)
> retry = 1800 (30M)
> expire = 604800 (1W)
> minimum ttl = 86400 (1D)
>
> ------------
> 101.228.214.206.in-addr.arpa
> ttl = 86400 (1D)
> origin = vast.urbanna.net
> mail addr = root.urbanna.net
> serial = 20000824
> refresh = 10800 (3H)
> retry = 1800 (30M)
> expire = 604800 (1W)
> minimum ttl = 86400 (1D)
> ;; res_nmkquery(QUERY, 2.228.214.206.in-addr.arpa, IN, PTR)
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 51921, rcode = NOERROR
> header flags: response, auth. answer, want recursion, recursion avail.
> questions = 1, answers = 2, authority records = 1, additional = 1
>
> QUESTIONS:
> 2.228.214.206.in-addr.arpa, type = PTR, class = IN
> ANSWERS:
> -> 2.228.214.206.in-addr.arpa
> name = myhost.ccsinc.com
> ttl = 86400 (1D)
> -> 2.228.214.206.in-addr.arpa
> name = mail.ccsinc.com
> ttl = 86400 (1D)
> AUTHORITY RECORDS:
> -> 228.214.206.in-addr.arpa
> nameserver = myhost.ccsinc.com
> ttl = 86400 (1D)
> ADDITIONAL RECORDS:
> -> myhost.ccsinc.com
> internet address = 206.214.228.2
> ttl = 86400 (1D)
>
> ------------
> Server: myhost.ccsinc.com
> Address: 206.214.228.2
>
> ;; res_nmkquery(QUERY, vast.urbanna.net, IN, A)
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 51922, rcode = NOERROR
> header flags: response, want recursion, recursion avail.
> questions = 1, answers = 1, authority records = 1, additional = 1
>
> QUESTIONS:
> vast.urbanna.net, type = A, class = IN
> ANSWERS:
> -> vast.urbanna.net
> internet address = 206.214.228.101
> ttl = 82264 (22h51m4s)
> AUTHORITY RECORDS:
> -> urbanna.NET
> nameserver = vast.urbanna.net
> ttl = 9845 (2h44m5s)
> ADDITIONAL RECORDS:
> -> vast.urbanna.net
> internet address = 206.214.228.101
> ttl = 82264 (22h51m4s)
>
> ------------
> Non-authoritative answer:
> Name: vast.urbanna.net
> Address: 206.214.228.101
>
> --
> Public Key at http://pgpkeys.mit.edu:11371
> Public Key Encryption? http://www.cryptography.org/getpgp.htm
> If you don't have it, you need it.
More information about the bind-users
mailing list