[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 431
  • Last Modified:

bind down....not working

I have no idea why but Bind failed.

Steps:
1. Named is on in service manager
2. updated cpanel to R119 (9.9.8)
3. /scripts/./fixndc (tells me already fixed)
4. Restarted BIND
5. /scripts/updatenow
6. /scripts/fixnamed
7. rndc reload

Please help

OS: Fedora Core 1
cPanel / WHM 9.9.8 R119
0
SecretAgentOnline
Asked:
SecretAgentOnline
  • 4
  • 4
  • 2
  • +1
3 Solutions
 
wesly_chenCommented:
Hi,

   Any error message from /var/log/messages?
   Any recently change on the named.conf or DNS record files?

Wesly
0
 
SecretAgentOnlineAuthor Commented:
Here's a piece I think may help you figure it out (thanks)

Nov 21 10:21:46 server named:  succeeded
Nov 21 10:21:46 server named[14557]: starting BIND 9.2.4rc6 -u named
Nov 21 10:21:46 server named[14557]: using 1 CPU
Nov 21 10:21:46 server named: named startup succeeded
Nov 21 10:21:46 server named[14557]: loading configuration from '/etc/named.conf'
Nov 21 10:21:46 server named[14557]: no IPv6 interfaces found
Nov 21 10:21:46 server named[14557]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 21 10:21:46 server named[14557]: listening on IPv4 interface eth0, 216.32.66.106#53
Nov 21 10:21:46 server named[14557]: listening on IPv4 interface eth0:1, 216.32.66.107#53
Nov 21 10:21:46 server named[14557]: could not listen on UDP socket: shutting down
Nov 21 10:21:46 server named[14557]: creating IPv4 interface eth0:1 failed; interface ignored
Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:2, 216.32.66.108#53
Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:2 failed; interface ignored
Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:3, 216.32.66.109#53
Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:3 failed; interface ignored
Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:4, 216.32.66.110#53
Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:4 failed; interface ignored
Nov 21 10:21:47 server named[14557]: cache.c:497: unexpected error:
Nov 21 10:21:47 server named[14557]: isc_task_create() failed: shutting down
Nov 21 10:21:47 server named[14557]: loading configuration: unexpected error
Nov 21 10:21:47 server named[14557]: exiting (due to fatal error)
Nov 21 10:21:47 server named: named shutdown succeeded
Nov 21 10:21:47 server named[14583]: starting BIND 9.2.4rc6 -u named
Nov 21 10:21:47 server named[14583]: using 1 CPU
Nov 21 10:21:47 server named[14583]: loading configuration from '/etc/named.conf'
Nov 21 10:21:47 server named[14583]: no IPv6 interfaces found
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface eth0, 216.32.66.106#53
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface eth0:1, 216.32.66.107#53
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface eth0:2, 216.32.66.108#53
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface eth0:3, 216.32.66.109#53
Nov 21 10:21:47 server named[14583]: listening on IPv4 interface eth0:4, 216.32.66.110#53
Nov 21 10:21:47 server named[14583]: command channel listening on 127.0.0.1#953
Nov 21 10:21:47 server named[14583]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
0
 
wesly_chenCommented:
Hi,

> Nov 21 10:21:46 server named[14557]: listening on IPv4 interface eth0:1, 216.32.66.107#53
> Nov 21 10:21:46 server named[14557]: could not listen on UDP socket: shutting down
> Nov 21 10:21:46 server named[14557]: creating IPv4 interface eth0:1 failed; interface ignored
> Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:2, 216.32.66.108#53
> Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
> Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:2 failed; interface ignored
> Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:3, 216.32.66.109#53
> Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
> Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:3 failed; interface ignored
> Nov 21 10:21:47 server named[14557]: listening on IPv4 interface eth0:4, 216.32.66.110#53
> Nov 21 10:21:47 server named[14557]: could not listen on UDP socket: shutting down
> Nov 21 10:21:47 server named[14557]: creating IPv4 interface eth0:4 failed; interface ignored

It seems that you have 4 virtual IPs on the eth0 (eth0:1, eth0:2, eth0:3, eth0:4) and those virtual IP doesn't
accept UDP.

However, the following messages show named is up and listening on all the IPs.

Could you provide:
# ifconfig -a
And the way you test DNS?

Wesly
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
SecretAgentOnlineAuthor Commented:
I didn't test it, restarting BIND gives no error but the error is in server status inside web host manager (cpanel's admin side)

ifconfig -a shows this:

eth0      Link encap:Ethernet  HWaddr 00:11:11:41:E5:34
          inet addr:216.32.66.106  Bcast:216.32.66.111  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3000201 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3712727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:597271326 (569.6 Mb)  TX bytes:3724442339 (3551.9 Mb)
          Interrupt:3 Base address:0xdc00 Memory:ff8ff000-ff8ff038

eth0:1    Link encap:Ethernet  HWaddr 00:11:11:41:E5:34
          inet addr:216.32.66.107  Bcast:216.32.66.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3000201 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3712727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:597271326 (569.6 Mb)  TX bytes:3724442339 (3551.9 Mb)
          Interrupt:3 Base address:0xdc00 Memory:ff8ff000-ff8ff038

eth0:2    Link encap:Ethernet  HWaddr 00:11:11:41:E5:34
          inet addr:216.32.66.108  Bcast:216.32.66.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3000201 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3712727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:597271326 (569.6 Mb)  TX bytes:3724442339 (3551.9 Mb)
          Interrupt:3 Base address:0xdc00 Memory:ff8ff000-ff8ff038

eth0:3    Link encap:Ethernet  HWaddr 00:11:11:41:E5:34
          inet addr:216.32.66.109  Bcast:216.32.66.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3000201 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3712727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:597271326 (569.6 Mb)  TX bytes:3724442339 (3551.9 Mb)
          Interrupt:3 Base address:0xdc00 Memory:ff8ff000-ff8ff038

eth0:4    Link encap:Ethernet  HWaddr 00:11:11:41:E5:34
          inet addr:216.32.66.110  Bcast:216.32.66.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3000201 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3712727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:597271326 (569.6 Mb)  TX bytes:3724442339 (3551.9 Mb)
          Interrupt:3 Base address:0xdc00 Memory:ff8ff000-ff8ff038

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:173036 errors:0 dropped:0 overruns:0 frame:0
          TX packets:173036 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:43024321 (41.0 Mb)  TX bytes:43024321 (41.0 Mb)
0
 
wesly_chenCommented:
> BIND gives no error but the error is in server status inside web host manager (cpanel's admin side)
Could you provide the errot messages of cpanel?

Besides, can you just do
$ nslookup www.yahoo.com
to test DNS?

Wesly
0
 
SecretAgentOnlineAuthor Commented:
root@tungsten [~]# $ nslookup www.yahoo.com
-bash: $: command not found

in whm server status it shows
bind (9.2.4rc6) failed
0
 
SecretAgentOnlineAuthor Commented:
Ok, its actually nslookup (enter)

I got this:

root@tungsten [~]# nslookup
www.yahoo.com
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
www.yahoo.com   canonical name = www.yahoo.akadns.net.
Name:   www.yahoo.akadns.net
Address: 216.109.118.76
Name:   www.yahoo.akadns.net
Address: 216.109.118.78
Name:   www.yahoo.akadns.net
Address: 216.109.117.108
Name:   www.yahoo.akadns.net
Address: 216.109.117.109
Name:   www.yahoo.akadns.net
Address: 216.109.117.206
Name:   www.yahoo.akadns.net
Address: 216.109.118.69
Name:   www.yahoo.akadns.net
Address: 216.109.118.72
Name:   www.yahoo.akadns.net
Address: 216.109.118.75
0
 
wesly_chenCommented:
So your DNS (BIND) has no problem, since you can querry www.yahoo.com.
The problem is something else.
Check the setting of the application which has problem with DNS.

Wesly
0
 
Nemesis-ServicesCommented:
sounds like it could be a firewall issue as the udp port 53 isn't binding to any of the virtual ip addresses, also listen to a certain IP address:

listen-on { xx.xx.xx.xx; };
0
 
cyb3rj0hnCommented:
Usually errors like this are generated when the shutdown of named did not complete successfully, meaning you still had an instance of named running.  DNS is heavily dependent on UDP so if you seen errors like this it cannot bind UDP on port 53 for that IP instance because there is already a named daemon bound to it that is still running. One other thing to mention if you have a lot of DNS entries, named will take some time to shut down, even though it has already showed you an "OK". Use ps ax|grep named to make sure it has completly shut down.  Hope this helps.

Cheers,
John
0
 
Nemesis-ServicesCommented:
Hi Venabili,

I would suggest splitting the points between the experts in this question ? :)
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 4
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now