Dig gives ;; connection timed out; no servers could be reached-

[Sebastian Castro]

On Tue, Jan 01, 2002 at 05:02:51PM -0600, Cris Rhea wrote:
> 
> > When I reload named, I no errors in the log
> > 
> > Dec 30 14:41:12 ham named: named startup succeeded
> > Dec 30 14:41:12 ham named[13909]: no IPv6 interfaces found
> > Dec 30 14:41:12 ham named[13909]: listening on IPv4 interface lo,
> > 127.0.0.1#53
> > Dec 30 14:41:12 ham named[13909]: listening on IPv4 interface eth0,
> > 192.168.113.33#53
> > Dec 30 14:41:12 ham named[13909]: listening on IPv4 interface eth1,
> > 208.184.11.178#53
> > Dec 30 14:41:12 ham named[13909]: command channel listening on 127.0.0.1#953
> > Dec 30 14:41:13 ham named[13909]: running
> 
> You have no errors here, syntax or otherwise... ;)
> 
> Aside from the comments others have made regarding improvments in your
> config files, I'd be looking at the iptables configs rather than 
> BIND configs. 
> 
> Your server isn't answering queries (or the queries aren't getting to
> the BIND software). 
> 
> Since you didn't say how you configured iptables (ipCHAINS is enabled
> by default in RH7.2), I can't say where the problem might be, but your
> symptoms indicate to me that it's a firewall issue and not just a BIND
> issue.
> 

A way to test this is try to telnet to the host using the port used by BIND

For example, if you were trying

dig ns mydomain.com @127.0.0.1 and got "no servers available"

try 

telnet 127.0.0.1 53

or 

telnet 0 53

If you get "connection refused", the problem is IP Tables for sure.


I hope I've helped


Best Regards

--
Sebastian E. Castro Avila             sebastian at nic.cl
DNS Manager, NIC Chile 
"We are .CL"