The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

"Add an A entry to my hostname" Broke My Server. Help!

Discussion in 'General Discussion' started by RTCruiser, Aug 24, 2006.

  1. RTCruiser

    RTCruiser Active Member

    Joined:
    Jun 28, 2006
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    This is a lesson in "if it ain't broke, don't fix it!" for me.

    My server has been working fine since I got it a few months ago. Yesterday I was in WHM and I changed an MX record for a client so he could use another server for his email. While I was in the DNS Functions area I impusively clicked on the "Add an A entry to my hostname" link then confirmed the request. (I should note my hostname already had an A entry.) WHM reported it couldn't restart BIND, and ever since then my hosted Web sites are down and the mail server is also down.

    I got an email sent to me from cpanel that reads:

    ===========================================
    "[ipcheck] Problems with dns setup on hostname.mydomain.com

    IMPORTANT: Do not ignore this email.
    The hostname (hostname.mydomain.com) resolves to . It should resolve to 00.000.00.70. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.

    Some are all of these problems can be caused by
    /etc/resolv.conf being setup incorrectly. Please check this file if you
    believe everything else is correct."
    ===============================================

    (I changed the hostname, domain name and IP address in the paste above).


    When I open up resolv.conf it lists my primary and secondary DNS servers like so:

    nameserver 000.000.000.01
    nameserver 000.000.000.02

    and that's it. Should there be something else there?


    Please help, and I promise never to click that link again! :)
     
  2. RTCruiser

    RTCruiser Active Member

    Joined:
    Jun 28, 2006
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    Fixed!

    First off let me say I KNOW there have been many other similar threads on this issue. I tried them all and none of them worked for me.

    I finally got this resolved by getting ahold of a knowledgeable tech support person at my hosting company (EV1).

    A previous post by AndyReed came the closest to solving the problem. He wrote:

    But for me, updatenow said it couldn't be run from root and fixndc ran but didn't fix the problem.

    The EV1 tech ran /scripts/fixrndc which immediately corrected the problem.

    Just an FYI for the many others that will surely run into this issue again.

    BTW, why is the "Add an A record ..." link there if it breaks servers so often?
     
Loading...

Share This Page