LinuxQuestions.org - DNS Problem

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - DNS Problem (https://www.linuxquestions.org/questions/debian-26/dns-problem-511542/)

After my server has been running a while the DNS stops responding so i go to http://www.dnsreport.com/tools/dnsre...in=3gxlive.com and check it and i receive the error:

Quote:

A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

The server has not been running very long at all either

Quote:

ns1:~# uptime
14:28:30 up 2:11, 1 user, load average: 0.00, 0.11, 0.12

Is there maybe something in the BIND config i can change to it does not do this? This is also odd because the majority of the time when i login to my server using PuTTY then it makes the DNS respond again. Any help would be much appriciated.

It does this to all hosted sites:
http://www.3gxlive.com
http://www.trickmodz.com

The problem is not related to your machine: the error states that the other server didn't respond. You could have deducted this yourself, if you'd read the error message more carefully ;)

as a matter of fact it is my server that is not responding..it is my dns server which is on my own machine..i use a hosting control panel but no matter which one it is this always happens.. the error states "None of YOUR nameservers responded fast enough." so yes this is an error due to something in my system but what? i dont know..and no matter which version of BIND i use the same thing always happens

Quote:

Originally Posted by ballistic509

You should be getting some log diagnostics if Bind is halting. Usually in /var/log/named.log
Hopefully that will say why it's quitting. As a side note, when it stops answering (when the web site says it took too long to answer) is Bind still running? In RH-based distros:
service named status
If it's actually running and the web site says it's not answering, maybe a firewall issue? Or are you running this on a dynamic IP address such as cable/DSL?

actually i cannot find a log file for BIND in the /var/log/ directory..when this eror occurs BIND is still running..im running through a router with all ports to my server open and configured correctly, and also my ip is not changing at all..

Quote:

Originally Posted by ballistic509

It may be logging in messages, but to make things easier you may want to set it to use a different log.
I have to think that if the daemon is still running when the web page says it's taking too long there has to be something else in the middle halting it.