Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Bind somehow changed after cpupdate

Discussion in 'Bind/DNS/Nameserver' started by Frankc, Jun 15, 2008.

  1. Frankc

    Frankc Well-Known Member

    Joined:
    Jun 18, 2005
    Messages:
    103
    Likes Received:
    1
    Trophy Points:
    168
    We already ran our servers for a few years and never experienced a problem like this so can someone help pls?

    Our domain registrar REQUIRE correct nameserver setup, even the number of nameservers, before they register a new domain but after the last cpanel update (manually to both stable and then release) nameserver 4 don't respond.

    With starting bind I got the following/

    eth1:1, xx.xxx.xx.83#53 Jun 15 08:29:50 mercury named[17599]: listening on IPv4 interface eth1:2, xx.xxx.xx.84#53 Jun 15 08:29:50 mercury named[17599]: listening on IPv4 interface eth1:3, xx.xxx.xx.85#53 Jun 15 08:29:50 mercury named[17599]: listening on IPv4 interface eth1:4, xx.xxx.xx.86#53 Jun 15 08:29:50 mercury named[17599]: command channel listening on 127.0.0.1

    Dig from within the system gave the correct results but dig from outside give a timeout error on nameserver 4.

    http://ns4.sa-servers.net also don't show any results while http://ns3.sa-servers.net works correctly. (RDNS is correct and IP address point to ns4.sa-servers.net)

    There is already a few pending domain registrations so any help would be appreciated please.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice