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.

Nameservers not resolving to an IP

Discussion in 'Bind / DNS / Nameserver Issues' started by CaptainC, Sep 10, 2012.

  1. CaptainC

    CaptainC Registered

    Joined:
    Sep 5, 2012
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    When I recieved my VPS I added two nameservers on seperate IP's

    so i had

    ns1.mydomain.co.uk 123.123.123.123
    ns2.mydomain.co.uk 123.123.123.124

    created the A records

    all via the basic set up screen. I then added a few accounts and everything appeared fine for a short time.

    and I created a hostname server.mydomain.co.uk

    I then get the following

    Your hostname (server.mydomain.co.uk) could not be resolved to
    an IP address. This means that /etc/hosts is not set up correctly,
    and/or there is no dns entry for server.corbywebworx.co.uk. Please
    be sure that the contents of /etc/hosts are configured correctly,
    and also that there is a correct 'A' entry for the domain in the
    zone file. etc.

    So here's the rub!

    What I didn't realise (yes understand) was that the VPS provider provided a slave dns and the VPS was already set up with ns1.ahost.net and ns2.ahost.net.

    When I check the nameserver IP's I have

    ns1.ahost.net 123.123.123.123 2
    ns1.mydomain.co.uk No IP 15
    ns2.ahost.net 123.123.123.124 2
    ns2.mydomain.co.uk No IP 15

    What is the best solution to reverse this problem? Having my own nameservers is not essential and I now understand about the slave DNS.
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    653
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page