Really weird nameserver/DNS issue

Discussion in 'Web Hosting' started by sarahk, Sep 25, 2012.

  1. #1
    I'm just in the process of moving some sites from one shared server to another, done it before, hate the process. The nameservers on the old machine were ns3 and ns4. On the new machine I've got ns6 and ns4

    Some of the domains have moved over seamlessly but I have four weird ones - registered at Dynadot (1) and Namecheap (3)

    If I ping www. mysite.com I get the old server IP back
    If I ping mysite.com I get the new server IP

    When I visit the site I get the different servers depending on which domain I request.

    Why have these not propograted at the same time? How do I get them to match?
     
    sarahk, Sep 25, 2012 IP
  2. briteday

    briteday Active Member

    Messages:
    358
    Likes Received:
    5
    Best Answers:
    1
    Trophy Points:
    70
    #2
    Hmmm, I think I would contact your new name server support. It is common for domain.com to map to www.domain.com, but is not required by DNS, or built in. Regardless, they should have the answer for you. Good Luck!
     
    briteday, Sep 25, 2012 IP
  3. RHS-Chris

    RHS-Chris Well-Known Member

    Messages:
    1,007
    Likes Received:
    35
    Best Answers:
    10
    Trophy Points:
    150
    #3
    Hello there,

    The www "A" records always seem to take longer to propagate, as they generally have a higher TTL (time to live). How long has it been since you changed the name servers? Did you also remember to change the IP assigned to NS4 at your registrar as well as where the domain itself is hosted?

    Regards,
    Chris
     
    RHS-Chris, Sep 25, 2012 IP
  4. sarahk

    sarahk iTamer Staff

    Messages:
    28,808
    Likes Received:
    4,535
    Best Answers:
    123
    Trophy Points:
    665
    #4
    OK, that's interesting... I'll give it some more time :)
     
    sarahk, Sep 25, 2012 IP
  5. RonBrown

    RonBrown Well-Known Member

    Messages:
    934
    Likes Received:
    55
    Best Answers:
    4
    Trophy Points:
    105
    #5
    That's exactly what it will be. Since you get the new server for <domain> but not for www.<domain> show that it is working and it's a caching issue somewhere - your browser or the DNS servers you are using for your personal internet connection. The reason your seeing the correct <domain> connection is that you probably don't connect to that version of the domain (you usually use www.<domain>) so your search for <domain> caused a new DNS request and it returned the latest IP address. It normally doesn't take too long to resolve itself.
     
    RonBrown, Sep 26, 2012 IP