0

I've recently moved from a shared hosting to a VPS at vps.net but I think I might have broken it already!

I have domain.com and domain.net. I have setup DNS records for both to point to my server. However, only domain.com pings to the correct IP address. domain.net is pointing to a different IP address. Possibly the old server it was pointing to. This has now been deleted.

Is there possibly any way to correct this without having to submit a ticket to VPS.net?

fatnic
  • 101
  • 2

1 Answers1

1

It could be that the other name change has not yet propagated to your local (ad ISP) DNS cache, and you are just lucky that the other change became available as quick. Give it a little time, for the cached entries to be refreshed, then try again.

All DNS entries have a time-to-live value (TTL) which is how many seconds a DNS server should cache them for, most registrars let you change this though some don't. Typical defaults (or fixed values if the registrar doesn't let you control it) for TTL are 24 hours and 4 hours - it used to be that 24 was most common by far but shorter values seem to be becoming more normal these days.

When your machine asks your ISP's DNS servers (or Google's, or OpenDNS's, if you use such services) for the address associated with a name it will only check for the latest value if it has no value locall stored or that value has passed its TTL time since it was last checked. So if the TTL for your entries is 24 hours then it will take up to 24 hours for your ISP to see any change, but you might be lucky and find the cached enty is due to expire soon so it takes a far shorter time.

David Spillett
  • 22,754
  • 45
  • 67
  • 1
    +1 You can perform a whois query to find out which nameservers the domain is configured to use and then query those directly to find out which ip address they're returning (something like dig domain.com @ns1.dnsprovider.com). That should give you something more to go on. – WheresAlice Apr 10 '10 at 16:20