You will get this if
1. named is not running.
2. named did not create the control socket due to syntax errors in
named.conf. Check your logs.
3. you have told named (via named.conf) to use a different socket.
ndc -c
You will get this if
1. named is not running.
2. named did not create the control socket due to
syntax errors in
named.conf. Check your logs.
3. you have told named (via named.conf) to use a
different socket.
ndc -c
On Mon, 20 Aug 2001, Justin Funke wrote:
Has anyone else seen this. It happened amongst my flurry of upgrades this
weekend. Now I cannot resolve any DNS names.
After any package upgrades, unless you know specific less disruptive
command, you should always do:
/sbin/e-smith/signal-event
On Mon, 20 Aug 2001, Charlie Brady wrote:
On Mon, 20 Aug 2001, Justin Funke wrote:
Has anyone else seen this. It happened amongst my flurry of upgrades this
weekend. Now I cannot resolve any DNS names.
After any package upgrades, unless you know specific less disruptive
command [...]
Another clue,
(the not working server)
named31585 0.0 2.6 2724 1672 ?S11:09 0:00 named -u
named
(my other regular working server)
dns 1622 0.0 0.9 3052 2072 ?S11:01 0:00
/usr/sbin/named -
- Both named startup scripts are identical in between the two
On Mon, 20 Aug 2001, Justin Funke wrote:
Has anyone else seen this. It happened amongst my flurry of upgrades this
weekend. Now I cannot resolve any DNS names.
# ping www.e-smith.com
ping: unknown host www.e-smith.com
# service named status
ndc: error: ctl_client: evConnect(fd 3):
Turns out a Microsoft solution fixed my e-smith server :)
Microsoft TechNet Knowledge Base Article 000-1
When all else fails reboot the server.
Everything working now.
The interesting side note on this was that I had thought I was remotely
rebooting the server on several other occasions
