DNS Update

Domain doesn't resolve at all during propagation?

[woop01]

We have made numerous DNS updates in the past. In each one of them it obviously took time for the domain to stop resolving to the old IP and start resolving to the new IP. However, we have never had a situation where during that process the domain failed to resolve at all until now.

We made the change early today and while the domain no longer resolves to the old IP, it just flat out doesn't resolve at all. When we do a ping from five different locations in the United States we get "Ping could not find host domain.com. Please check the name and try again."

Network Solutions is telling me that this is normal and is part of the resolving process although we have never seen it before. Have I just been lucky in the past to never catch a domain during the part where it stops resolving altogether or are we being fed some lies?

[Webwork]

I've moved a lot of domains around. :)

I've had a similar experience, though it's the exception not the rule and it was more of a problem several years ago than recently.

How long before it finally resolved?

[davezan]

Did you completely switch from one set of DNS to another, or did you change the DNS' IP addresses?

Assuming netsol did submit the changes and it reflects on most if not all DNS "checkers", it's probably a matter of time.

Of course, there can be other factors involved on why a domain isn't resolving to its intended destination. Why not check those "other factors" as well just to scratch them off your list?

[woop01]

It took 21 hours from the time we started the update to move the new IP. That's not an issue, the problem is the domain didn't resolve at all for 16 of those hours. I've just never seen a domain go completely down for that long during a DNS update.

Thankfully, this domain is pre-development and not an active site as of this moment.