The Texas Regional Hostmaster FAQ : Interpreting the Diagnostic Output from the Technical Check Process : What does the error “No name server is running (connection refused)” mean?
This error means that the technical checks were unable to find a name server running on the host being checked. This is usually caused by one or more of the following: • The name server daemon is actually not running at all. It must be started before these checks are run again. • The name server daemon is not reachable from the Internet because there is a firewall or filtering router that is blocking connections to port 53 on this host for both UDP and TCP connections. The firewall configuration must permit connections on this port from any host on the Internet for the DNS to function properly. • The name server daemon does not support TCP connections for DNS transactions. This is a violation of RFC 1034/1035. The name server software is defective and must be replaced.
Related Questions
- The Texas Regional Hostmaster FAQ : Interpreting the Diagnostic Output from the Technical Check Process : What does the error "No name server is running (connection refused)" mean?
- The Texas Regional Hostmaster FAQ : Interpreting the Diagnostic Output from the Technical Check Process : What does "Checking if zone ZONE.NAME.HERE.us is installed: No." mean?
- The Texas Regional Hostmaster FAQ : Interpreting the Diagnostic Output from the Technical Check Process : What does "No SOA Record found on the primary name server" mean?
