Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to set DNS forwarders for OpenDNS in named.conf file. After editing and saving the file, I tried reloading the BIND config with command: rndc reload. However, I am getting the error:

rndc: connect failed: connection refused

Does anyone know how to resolve this?

share|improve this question
here's named.conf file, will post LISTEN results next ... – user115009 Mar 22 '12 at 20:57
sh-3.2# nano named.conf GNU nano 2.0.6 File: named.conf keys { "rndc-key"; }; }; options { include "/etc/dns/"; /* * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked * questions using port 53, but BIND 8.1 uses an unprivileged * port by default. */ // query-source address * port 53; – user115009 Mar 22 '12 at 21:02
//forwarders {; ; }; //... }; // // a caching only nameserver config // logging { include "/etc/dns/"; }; // Public view read by Server Admin include "/etc/dns/"; // Server Admin declares all zones in a view. BIND therefore dictates // that all other zone declarations must be contained in views. – user115009 Mar 22 '12 at 21:02
what does these commands do?sudo launchctl stop org.isc.named sudo launchctl start org.isc.named – user115009 Mar 22 '12 at 21:20
it's resolved, thanks! – user115009 Mar 22 '12 at 23:10

It seems rndc is failing to connect to your BIND server on that interface/port. Is it listening?

sudo lsof -i | grep LISTEN

You may need to look in the controls statement of your BIND config to see how or if it's setup. Something like this:

controls {
    inet allow { localhost; }

Is it the built-in named? If so try to restart it this way:

sudo launchctl stop org.isc.named
sudo launchctl start org.isc.named
share|improve this answer

BIND name server might be running at a different port then the default port 953.

Often it is running at port 54.

Your BIND name server reload command then becomes:

$ sudo rndc -p 54 reload
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.