Re: DNS Problem: BIND on new NS Won't Respond
hi ya
On Sun, 3 Apr 2005, Hal Vaughan wrote:
> Apr 3 23:49:34 nserver named[5280]: hint zone "" (IN) loaded (serial 0)
not good
> Apr 3 23:49:34 nserver named[5280]: master zone "localhost" (IN) loaded
> (serial 1)
good
> Apr 3 23:49:34 nserver named[5280]: master zone "127.in-addr.arpa" (IN)
> loaded (serial 1)
good .. but you should use 0.0.127.in-addr.arpa in the file that created
this reverse dns
> Apr 3 23:49:34 nserver named[5280]: master zone "0.in-addr.arpa" (IN) loaded
> (serial 1)
bad ... you probably do not have ip# that start with "0.x.y.z"
> Apr 3 23:49:34 nserver named[5280]: master zone "255.in-addr.arpa" (IN)
> loaded (serial 1)
bad ... you probably do not have ip# that start with "255.x.y.z"
> Apr 3 23:49:34 nserver named[5280]: master zone "thresh.lan" (IN) loaded
> (serial 1)
bad ... tld of ".lan" is not legal
> Apr 3 23:49:34 nserver named[5280]: master zone "7.16.172.in-addr.arpa" (IN)
> loaded (serial 1)
good
> Apr 3 23:49:34 nserver named[5280]: listening on [127.0.0.1].53 (lo)
good
> Apr 3 23:49:34 nserver named[5280]: listening on [172.16.7.2].53 (eth0)
good
> Apr 3 23:49:34 nserver named[5280]: listening on [192.168.100.202].53
> (eth0:0)
good
but you're mssing the reverse dns of 100.168.192.in-addr.arpa
> Apr 3 23:49:34 nserver named[5280]: Forwarding source address is [::].33281
havn't seen that before
> Apr 3 23:49:34 nserver named[5280]: Forwarding source address is
> [0.0.0.0].33282
bad
> Apr 3 23:49:34 nserver named[5281]: Ready to answer queries.
bad .. misleading messages for a misconfigured dns server
> So what am I doing wrong that bind/named doesn't even seem to respond to
> requests from dig?
post all your dns zone files
c ya
alvin
Reply to: