DNS help Please!

Kevin Darcy kcd at daimlerchrysler.com
Fri Sep 8 23:48:47 UTC 2000


Because dig is far superior to nslookup. Unlike nslookup, dig doesn't croak if it
is unable to reverse-resolve the nameserver's IP address.

You _do_ need figure out what's up with your reverse zone, though. If a nameserver
isn't answering authoritatively for one of its zones, it's probably because the
zone didn't load properly, most likely because of some sort of syntax error in the
zone file. Look in the master server's logfile for the cause.


- Kevin

Gerald Waugh wrote:

> I just attempted the command, (from an ssh session on frontstreetnetworks.net)
>
> [root log]# nslookup @fsn1.frontstreetnetworks.net fsn1.frontstreetnetworks.net
> With this response
> *** Can't find server name for address 216.175.178.41: Timed out
> *** Default servers are not available
>
> This is what was in the log;
>
> Sep  8 19:30:21 fsn1 named[369]: ns_forw:
> query(41.32-28.178.175.216.in-addr.arpa)
>  All possible A RR's lame
> Sep  8 19:31:02 fsn1 named[369]: Err/TO getting serial# for
> "32/28.178.175.216.in-
> addr.arpa"
> Sep  8 19:31:02 fsn1 named-xfer[17580]: [216.175.178.41] not authoritative for
> 32/
> 28.178.175.216.in-addr.arpa, SOA query got rcode 0, aa 0, ancount 0, aucount 2
> --------------------------------------------------------------------------------
> ------------------------------------------
> Then I tried [root log]# dig @fsn1.frontstreetnetworks.net
> fsn1.frontstreetnetworks.net
> with this result:
>
> ; <<>> DiG 8.2 <<>> @fsn1.frontstreetnetworks.net fsn1.frontstreetnetworks.net
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
> ;; QUERY SECTION:
> ;;      fsn1.frontstreetnetworks.net, type = A, class = IN
>
> ;; ANSWER SECTION:
> fsn1.frontstreetnetworks.net.  1D IN A  216.175.178.41
>
> ;; AUTHORITY SECTION:
> frontstreetnetworks.net.  1D IN NS  fsn1.frontstreetnetworks.net.
> frontstreetnetworks.net.  1D IN NS  fsn2.frontstreetnetworks.com.
> frontstreetnetworks.net.  1D IN NS  fsn3.frontstreetnetworks.com.
>
> ;; ADDITIONAL SECTION:
> fsn1.frontstreetnetworks.net.  1D IN A  216.175.178.41
> fsn2.frontstreetnetworks.com.  1D IN A  216.175.178.46
> fsn3.frontstreetnetworks.com.  1D IN A  216.175.178.45
>
> ;; Total query time: 13 msec
> ;; FROM: fsn1.frontstreetnetworks.net to SERVER: fsn1.frontstreetnetworks.net
> 216
> .175.178.41
> ;; WHEN: Fri Sep  8 19:34:52 2000
> ;; MSG SIZE  sent: 46  rcvd: 208
>
> Why does 'dig' seem to work but 'nslookup' fails! Also getting-sending mail from
> some of my accounts takes a very long time.
> I really am desperate to find a solution to this problem, as I don't think my
> reverse lookups are working.






More information about the bind-users mailing list