By AzraiL

Member
Jul 17, 2007
8
0
51
Hi all,

i have a problem nds.

Waiting for nsd to restart...............................................................finished.
nsd has failed, please contact the sysadmin (result was "nsd is not running").
Apr 6 15:15:01 server nsd[26624]: can't bind udp socket: Address already in use
Apr 6 15:15:01 server nsd[26624]: server initialization failed, nsd could not be started

bind working nds not working :(
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
42
348
somewhere over the rainbow
cPanel Access Level
Root Administrator
Try to check what is already running on the socket:

Code:
lsof -i :53
netstat -an | grep :53
 

By AzraiL

Member
Jul 17, 2007
8
0
51
[email protected] [~]# lsof -i :53
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
dnsmasq 5026 nobody 6u IPv4 20562 TCP 192.168.122.1:domain (LISTEN)
dnsmasq 5026 nobody 7u IPv4 20563 UDP 192.168.122.1:domain
named 29895 named 20u IPv4 592589 TCP localhost.localdomain:domain (LISTEN)
named 29895 named 21u IPv4 592591 TCP server.dev10.net:domain (LISTEN)
named 29895 named 22u IPv4 592593 TCP server.dev10.net:domain (LISTEN)
named 29895 named 23u IPv4 592595 TCP server.dev10.net:domain (LISTEN)
named 29895 named 24u IPv4 592597 TCP server.dev10.net:domain (LISTEN)
named 29895 named 512u IPv4 592588 UDP localhost.localdomain:domain
named 29895 named 513u IPv4 592590 UDP server.dev10.net:domain
named 29895 named 514u IPv4 592592 UDP server.dev10.net:domain
named 29895 named 515u IPv4 592594 UDP server.dev10.net:domain
named 29895 named 516u IPv4 592596 UDP server.dev10.net:domain
named 29895 named 517u IPv4 592598 UDP 192.168.122.1:domain

-------------------------------------------------------------------------------------------

[email protected] [~]# netstat -an | grep :53
tcp 0 0 85.17.159.210:53 0.0.0.0:* LISTEN
tcp 0 0 85.17.159.209:53 0.0.0.0:* LISTEN
tcp 0 0 85.17.159.208:53 0.0.0.0:* LISTEN
tcp 0 0 85.17.159.207:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN
tcp 0 0 85.17.159.207:80 41.102.183.147:53051 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53048 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53055 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53054 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53053 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53052 TIME_WAIT
tcp 0 0 85.17.159.207:80 41.102.183.147:53074 ESTABLISHED
tcp 0 0 85.17.159.207:80 41.102.183.147:53073 ESTABLISHED
tcp 0 0 85.17.159.207:80 41.102.183.147:53072 ESTABLISHED
tcp 0 0 85.17.159.207:5901 78.191.145.26:53663 ESTABLISHED
udp 0 0 192.168.122.1:53 0.0.0.0:*
udp 0 0 85.17.159.210:53 0.0.0.0:*
udp 0 0 85.17.159.209:53 0.0.0.0:*
udp 0 0 85.17.159.208:53 0.0.0.0:*
udp 0 0 85.17.159.207:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 192.168.122.1:53 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 :::5353 :::*
 

JaredR.

Well-Known Member
Feb 25, 2010
1,834
27
143
Houston, TX
cPanel Access Level
Root Administrator
Your output shows that named is running and listening on port 53, so nsd will not be able to start, since named and nsd use the same port. You can use only nsd or named, not both at the same time. What is your selection in Main >> Service Configuration >> Nameserver Selection? What do you want to use as your nameserver service, named or nsd?
 

By AzraiL

Member
Jul 17, 2007
8
0
51
nsd has failed, please contact the sysadmin (result was "nsd is not running").
Apr 15 17:21:03 server nsd[3004]: can't bind udp socket: Address already in use
Apr 15 17:21:03 server nsd[3004]: server initialization failed, nsd
could not be started

firstly whm -> Service Configuration -> Nameserver Selection page NSD
check and saved.
secondlywhm -> Restart Services -> DNS Server (BIND/NSD) and restart
but i got that error message.

what i have to do?
 

JaredR.

Well-Known Member
Feb 25, 2010
1,834
27
143
Houston, TX
cPanel Access Level
Root Administrator
Does /var/cpanel/usensd exist?

Code:
# ls -alh /var/cpanel/usensd
If it does not, touch it:

Code:
# touch /var/cpanel/usensd
Either /scripts/restartsrv_named or /scripts_restartsrv_nsd should see the file and restart nsd instead of named. After touching /var/cpanel/usensd, try the following:

Code:
# /etc/rc.d/init.d/named stop
# /scripts/restartsrv_nsd
If this does not help, please submit a ticket. It would be very difficult to offer any further advice in this situation without being able to log into the server and investigate directly.
 

By AzraiL

Member
Jul 17, 2007
8
0
51
Oke i ll use BIND i think NDS would be more faster then BIND but it doesnt work. i ll use BIND thanks alot.
 

JaredR.

Well-Known Member
Feb 25, 2010
1,834
27
143
Houston, TX
cPanel Access Level
Root Administrator
nsd is normally faster, and uses fewer resources. You can try selecting nsd, and the running the following command from the shell:

Code:
# /scripts/setupnameserver nsd --force
We would like to help you use nsd, if that is what you prefer, so you are always welcome to submit a ticket if you would still like to use nsd instead of named.