Re: DNS Problem: BIND on new NS Won't Respond
On Monday 04 April 2005 01:58 am, you wrote:
> 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
What's bad here? I saw it was loading a file, so I thought it was 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
I'll change that, then. I left that as the default from install.
> > 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"
Okay, so I'll kill that file (and the next one). Again, these were defaults
that were there on the install.
> > 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
It's for an internal LAN. I used that so there was no problem or confusion
with a real TLD. I've been using it on a different subnet for several years
(this DNS is the new one, on a different subnet, as I'm transferring
everything over to a new LAN).
> > 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
I don't have that because the nameserver on the old LAN handles it. In order
to make it easy to use ssh from the old LAN to the new one, I created an
eth0:0 on each computer on the new LAN (old is 192.168.100, new is 172.16.7),
so it was easier to deal with on the old subnet. Once I've got everything
transferred, then 192.168.100 address space will be gone.
> > 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
Okay, so it's misconfigured -- that's a big help, because getting this message
made me think bind wasn't responding because it just wasn't getting a signal.
> > 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
Will do that tomorrow. First, I'll make changes according to what you pointed
out (like getting rid of the files starting with 0 or 255 and changing the
db.127 to 127.0.0).
Thanks for the help. I'll see if the simple modifications from what you've
pointed out make a difference.
Hal
> c ya
> alvin
Reply to: