Network Error Could Not Listen On Udp Socket Permission Denied
Plans & Pricing Partners Support Resources Preview Forums Forums Quick Links Search Forums New Posts Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts Resources Resources Quick Links Search Resources Most Active Authors Latest Reviews Feature Requests Defects Menu Log in Sign up The Community Forums Interact with an entire community of cPanel & WHM users! cPanel Forums > Server Administration and Customization > Bind / DNS / Nameserver Issues > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. BIND error named[431]: could not listen on UDP socket: permission denied Discussion in 'Bind / DNS / Nameserver Issues' started by hicom, Mar 26, 2006. hicom Well-Known Member Joined: May 23, 2003 Messages: 272 Likes Received: 0 Trophy Points: 16 We are noticing on FreeBSD 5.4 i386 with the latest cPanel (stable and release). This happens on ALL our cPanel servers and backup DNS servers, no matter what release. In /var/log/messages we see the following error: Mar 26 10:25:32 ns3 named[431]: could not listen on UDP socket: permission denied Mar 26 10:25:32 ns3 named[431]: creating IPv4 interface de0 failed; interface ignored Mar 26 10:25:32 ns3 named[431]: could not listen on UDP socket: permission denied Mar 26 10:25:32 ns3 named[431]: creating IPv4 interface lo0 failed; interface ignored Mar 26 10:25:32 ns3 named[431]: not listening on any interfaces Mar 26 11:25:32 ns3 named[431]: could not listen on UDP socket: permission denied Mar 26 11:25:32 ns3 named[431]: creating IPv4 interface de0 failed; interface ignored Mar 26 11:25:32 ns3 named[431]: could not listen on UDP socket: permission denied Mar 26 11:25:32 ns3 named[431]: creating IPv4 interface lo0 failed; interface ignored Mar 26 11:25:32 ns3 named[431]: not listening on any interfaces Notice this occurs EVERY hour. This is not a cron scheduled, something is causing BIND to do this, but I couldn't put my hand on it. The servers seem work fine, and they respond to DNS requests (except to the few seconds when it happens). On different servers this happens at different times. I'm not sure if this is wide spread, but we noticed it on ALL our FreeBSD servers running cPanel. Any ideas ? As I said DNS remains working fine except to the seconds this happen. Thanks, Tamouh #1 hicom, Mar 26, 2006 AndyReed Well-Known Member PartnerNOC Joined: May 29, 2004 Messages: 2,222 Likes Received: 3 Trophy Points: 38 Location: Minneapolis, MN hicom said: We are noticing on FreeBSD 5.4 i386 with the lat
on a Windows Server, you might encounter the following error: "Could not listen on UDP socket : permission denied" after a Windows Update. The short version is this: there's another service listening on port 53 (DNS), which causes the Plesk DNS service to stop working. In this case, it's the DNS Server built in Windows Server that is automatically started after a Windows Update. Short solution: stop the DNS service, and then restart the Plesk DNS. You can test this, by doing the following. https://forums.cpanel.net/threads/bind-error-named-431-could-not-listen-on-udp-socket-permission-denied.51262/ Log in via a Remote Desktop connection to your server, and shut down the Plesk DNS service (using the system-tray icon, in the bottom right). Stop the Plesk DNS Service Select the DNS service, and stop it using the button on the right. Now run the following command through a command prompt (start > run > cmd) to see https://ma.ttias.be/namedbind-could-not-listen-on-udp-socket-permission-denied/ if another service is still listening on the DNS (53) port. netstat -an | find "53" Netstat DNS Port Listening The term "LISTENING" means there's a service active, that is accepting requests on port 53. Since you shut down the Plesk DNS service, something else is using this port. Go the service management in Windows Server (start > run > services.msc), and find the Microsoft DNS Service. Microsoft DNS Service Enabled/Started In the list, the DNS Server will probably be started. Right-click it, and choose "Stop". If this service is not started, another piece of DNS software is running on your server that's using up the DNS port. You can check the processlist/task manager to find out which one (popular ones are Bind or Named). Now run the same command as above, to see if another service is still listening on port 53. Netstat - No Open DNS Port Port 53 no longer shows a "LISTENING" status, which means any service running on port 53 is now closed. Re-open the Plesk Service Monitor, as s
] [ author ] * On 12.04.2012 04:44 PM, Todd Snyder wrote: > You can set https://lists.isc.org/pipermail/bind-users/2012-April/087358.html interface-interval to a low number to make BIND scan for new interfaces frequently: Interesting option! Weird thing is, the documentation as per /usr/share/doc/bind-9.9.0/html/Bv9ARM.ch06.html says: The server will scan the network interface list every interface-interval minutes. The default is 60 minutes. The maximum value is 28 days (40320 minutes). If set to 0, interface scanning will only occur network error when the configuration file is loaded. After the scan, the server will begin listening for queries on any newly discovered interfaces (provided they are allowed by the listen-on configuration), and will stop listening on interfaces that have gone away. So the default value is 60 minutes. In theory, I should see named binding to ppp0 after network error could about 60 minutes after the ppp0 interface gets up again. This never happened to me. I set the interval to zero and forced a reconfig/reload via rndc. I feel so stupid for not grepping the log file for ppp0 before, anyway, here's the culprit: 12-Apr-2012 17:03:38.661 general: info: received control channel command 'reconfig' 12-Apr-2012 17:03:38.661 general: info: loading configuration from '/etc/bind/named.conf' 12-Apr-2012 17:03:38.662 general: info: reading built-in trusted keys from file '/etc/bind/bind.keys' 12-Apr-2012 17:03:38.662 general: info: using default UDP/IPv4 port range: [1024, 65535] 12-Apr-2012 17:03:38.662 general: info: using default UDP/IPv6 port range: [1024, 65535] 12-Apr-2012 17:03:38.664 network: info: listening on IPv4 interface ppp0, 85.183.67.131#53 12-Apr-2012 17:03:38.664 network: error: could not listen on UDP socket: permission denied 12-Apr-2012 17:03:38.664 network: error: creating IPv4 interface ppp0 failed; interface ignored 12-Apr-2012 17:03:38.679 general: info: sizing zone task pool based on 6 zones 12-Apr-2012 17:03:38.680 database: debug 1: decrement_reference: delete from rbt: 0x7f667e609e28 . 12-Apr-2012 17:03:38.680 general: debug 1: managed-keys-zone: synchronizing trusted keys 12-Apr-2012 17:03:38.681 general: debug 1: now using logging configura