named: could not listen on UDP socket: address not available

Portal Home > Knowledgebase > Articles Database > named: could not listen on UDP socket: address not available

Posted by astraeuz, 03-09-2010, 09:09 PM
Hello, named, on our server is just listening on 1 IP address and none of the others are working, here are the lines from /var/log/messages for named when starting... Is it due to some wrong IP configuration in WHM?
Posted by jacksun, 03-09-2010, 09:48 PM
How many physical interfaces do you actually have (Looks like 1)? Have you assigned 8 different IP's as virtual interfaces on your 1 physical interface? Have you checked this config? Are the subnet masks correct (255.255.255.255 or 0.0.0.255 can't remember which cisco/bsd confused..)? It is working fine on localhost and your first and second interfaces (lo, eth0, eth0:1) but fails on eth0:2 and onward to eth0:7, which to me says it is failing on all virtual interfaces except the first, and working on your physical interface. Looks like something is wrong in the virtual interface setup for the eth0:2 > eth0:7, named sees eth0:1 when looking for these.
Posted by astraeuz, 03-09-2010, 11:43 PM
It looks there was something wrong with net mask or maybe something else i couldn't figure out, what i did is remove all the IPs from WHM's IP manager and added all of them back with the provided net mask... here is the log for named now... Now, if i take nslookup from ssh with one of the IP (x.x.x.38), it works fine which was not working earlier. However, if i try to do nslookup from my local home pc, it still can't reach this IP, neither with tracert. I contacted the DC with tracert, they say there is something wrong with your software configuration which we can't help you with Can you point to some direction?
Posted by jacksun, 03-10-2010, 12:27 AM
Ok, nslookup from SSH on one of your IP's is local, so if your config is correct there it will work. Now, nslookup from your home pc is a different thing. What nameserver are you using in nslookup? I always set mine to 8.8.8.8 unless I need to test something specific. This is googles name server. If you are getting no answer you and other DNS servers are not able to get info from your nameservers. Reason 1, does your domain have private nameservers set up with the correct IP's. 2) How long has it had to propogate? 3) do you have the proper ports open on your firewall to allow DNS queries to your nameservers? And by proper I mean the secure ones, don't just randomly open TCP/UDP port 53. Research this with your nameservers provider. 4) does your DNS zone for your domain have the proper entries for your nameservers? Hope this helps.

Add to Favourites Print this Article