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.

DNS Mess

Discussion in 'Bind / DNS / Nameserver Issues' started by roenick92, Jun 8, 2006.

  1. roenick92

    roenick92 Registered

    Joined:
    Jun 6, 2006
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Hello
    I'm in a bit of a bind with dns- I had an old server (celeron 1100 w/ red hat 9 & cpanel) and we upgraded to a new server (amd 64, centos 4 & cpanel) with a new IP. I had to email our hosting company about 8 times before I was informed by our hosting provider that the changes had been made for ns1 and ns2 pointing to my new server 2 days ago, and that it would take 24 - 48 hrs for them to propagate. Well, its been about 42 hrs, and checking with dnsstuff.com or internic.net shows ns1 and ns2 still pointing to the old IPs. I still have access to both servers, and in WHM on the old server, I can't delete ns1 or ns2 giving me this error:
    Sorry, the nameserver ip 69.72.xxx.xxx cannot be removing since it is still registered with an ICANN register.
    On the new server, I have ns1 and ns2 as 'A' records pointing to my new server (The new ip starts 65.98..), as well as on the old server (pointing to my new one with the same name). My question twofold:

    What's the best way to check what ns1 and ns2 resolve to?
    Is there anything I'm not doing to fix this problem myself through WHM? In other words- is this my problem all along, and my fault for not changing things? I can't access the account info at networksolutions because my hosting provider is the one who set it up and holds all the keys, so I figured it was up to them to change. Meanwhile I just got an email from cpanel on the old server telling me this:
    IMPORTANT: Do not ignore this email.
    The hostname (host.mydomain.com) resolves to . It should resolve to 69.72.xxx.xxx. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.
    (I just changed the host.mydomain.com and the actual IP).

    Any help on this would be really appreciated
    -Roenick92
     
  2. rhenderson

    rhenderson Well-Known Member

    Joined:
    Apr 21, 2005
    Messages:
    785
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Oklahoma
    cPanel Access Level:
    Root Administrator
    I would try it via dnsreport.com
     
  3. roenick92

    roenick92 Registered

    Joined:
    Jun 6, 2006
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Thanks for the website- I went there and tried my main domain, and this is what I got..

    ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:

    ns2.mydomain.com.:
    Parent server (m.gtld-servers.net) says A record is 69.72.xxx.xxx, but
    authoritative DNS server (69.72.xxx.xxx) says it is 65.98.xxx.xxx
    ns1.mydomain.com.:
    Parent server (m.gtld-servers.net) says A record is 69.72.xxx.xxx, but
    authoritative DNS server (69.72.xxx.xxx) says it is 65.98.xxx.xxx
    ns2.mydomain.com.:
    Parent server (m.gtld-servers.net) says A record is 69.72.xxx.xxx, but
    authoritative DNS server (69.72.xxx.xxx) says it is 65.98.xxx.xxx
    ns1.mydomain.com.:
    Parent server (m.gtld-servers.net) says A record is 69.72.xxx.xxx, but
    authoritative DNS server (69.72.xxx.xxx) says it is 65.98.xxx.xxx

    This means the problem is up the line, right? Not at my server? In other words when I shut down 69.72.xxx.xxx, I'll be completely lost to the internet?
    -Roenick92
     
Loading...

Share This Page