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!

one nameserver dead - any ideas?

Discussion in 'Bind/DNS/Nameserver' started by tjfulopp, Oct 23, 2005.

  1. tjfulopp

    tjfulopp Member

    Joined:
    Sep 22, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Slovakia / Belgium
    Hi

    I have two name servers
    * ns1.fulopp.org 216.237.127.250
    * ns2.fulopp.org 216.237.127.251

    Everything worked fine until now - ns2.fulopp.org is down somehow, I cannot ping it anymore.

    Looked over all settings in WHM and everything looks fine - any ideas? This is weird! I did not do any changes to the basic functionality lately, just adding some accounts, etc, also adding IPs (but not deleting any, and not touching the above ones).

    Please - anybody has any ideas as to what might be happening?
     
  2. bamasbest

    bamasbest Well-Known Member

    Joined:
    Jan 10, 2004
    Messages:
    531
    Likes Received:
    0
    Trophy Points:
    166
    Well,

    You can certainly restartt bind, but dnsreport indicates that you have no NS A records created. So, you may want to check your zone for fullop.org and ensure that it is correct rpior to a restart.
     
  3. tjfulopp

    tjfulopp Member

    Joined:
    Sep 22, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Slovakia / Belgium
    Yes, I did restart named.

    Thanks for the comment on the zone. However - I am not sure what to do in order to get the ns2 running (*.251). See attached screenshot of the DNS edit for fulopp.org. What precisely should I do?

    Thanks a million!!
     

    Attached Files:

  4. bamasbest

    bamasbest Well-Known Member

    Joined:
    Jan 10, 2004
    Messages:
    531
    Likes Received:
    0
    Trophy Points:
    166
    edit the zone for fullop and add A entries as follows:

    ns1 172800 IN A <ip.addy.for.ns1>
    ns2 172800 IN A <ip.addy.for.ns2>


    save, bind should auto reload, wait a little while and see what happens then!
     
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