Re: DNS Problem: BIND on new NS Won't Respond
On Monday 04 April 2005 12:17 am, Steven Jones wrote:
> Make sure there is no firewalling blocking dns in or out.
Nothing in iptables. I didn't (intentionally) install any firewalling. I'll
see if I can find anything else that could be firewalling. I can telnet to
port 53 on that system, so wouldn't that mean it's not firewalled off?
Thanks!
Hal
> Regards
>
> Thing
>
>
> -----Original Message-----
> From: Hal Vaughan [mailto:hal@thresholddigital.com]
> Sent: Monday, 4 April 2005 4:05 p.m.
> To: debian-user@lists.debian.org
> Subject: DNS Problem: BIND on new NS Won't Respond
>
> I'm running a nameserver for a small domain. I've written all the zone
> files
> and everything else. When I start bind, I get this in /var/log/syslog:
>
> Apr 3 23:49:34 nserver named[5280]: starting (/etc/bind/named.conf).
> named
> 8.4.6-REL-NOESW Tue Jan 25 19:11:36 UTC 2005
> ^Ilamont@mix:/build/lamont/bind-8.4.6/src/bin/named
> Apr 3 23:49:34 nserver named[5280]: hint zone "" (IN) loaded (serial 0)
> Apr 3 23:49:34 nserver named[5280]: master zone "localhost" (IN) loaded
>
> (serial 1)
> Apr 3 23:49:34 nserver named[5280]: master zone "127.in-addr.arpa" (IN)
>
> loaded (serial 1)
> Apr 3 23:49:34 nserver named[5280]: master zone "0.in-addr.arpa" (IN)
> loaded
> (serial 1)
> Apr 3 23:49:34 nserver named[5280]: master zone "255.in-addr.arpa" (IN)
>
> loaded (serial 1)
> Apr 3 23:49:34 nserver named[5280]: master zone "thresh.lan" (IN)
> loaded
> (serial 1)
> Apr 3 23:49:34 nserver named[5280]: master zone "7.16.172.in-addr.arpa"
> (IN)
> loaded (serial 1)
> Apr 3 23:49:34 nserver named[5280]: listening on [127.0.0.1].53 (lo)
> Apr 3 23:49:34 nserver named[5280]: listening on [172.16.7.2].53 (eth0)
> Apr 3 23:49:34 nserver named[5280]: listening on [192.168.100.202].53
> (eth0:0)
> Apr 3 23:49:34 nserver named[5280]: Forwarding source address is
> [::].33281
> Apr 3 23:49:34 nserver named[5280]: Forwarding source address is
> [0.0.0.0].33282
> Apr 3 23:49:34 nserver named[5281]: Ready to answer queries.
>
> So far, so good. It looks like the config files are loaded and
> everything is
> running fine. So I run dig:
>
> dig nserver
>
> ; <<>> DiG 9.2.4 <<>> nserver
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> >From what I can find, I cannot see why I get this instead of other
>
> errors.
> This error indicates to me that bind isn't even running, although when I
>
> check with ps -ax, it is running.
>
> So what am I doing wrong that bind/named doesn't even seem to respond to
>
> requests from dig?
>
> Thanks for any help!
>
> Hal
Reply to: