It should be a mystery to most...
When things break or have to move,
one problem is that old info can be provided when a system looks up
the numeric address for a given name. The data
for this lookup has timers on it. The timers let
a nameserver cache the information for a specified
length of time. If something changes behind the curtain
the old answer is assumed to be correct which can
result in a bad answer for as long as it takes for the
timers to expire and the authoritative servers to be checked.
You can have a local cache on your laptop, phone, or iPad.
Your ISP can have their copy.... eventually it will tidy
up.
If you plan to move the timers are set to be a lot shorter than
normal. This outage was not "planned".
Here is what it looks like now (five min ago) on a google
name server. The non-authoritative answer tells me
that this is a cached answer....
C:\Users\me>nslookup -type=ANY straightrazorplace.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
straightrazorplace.com
primary name server = ns49.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2011091504
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)
straightrazorplace.com nameserver = ns49.domaincontrol.com
straightrazorplace.com nameserver = ns50.domaincontrol.com
straightrazorplace.com internet address = 72.27.226.90
straightrazorplace.com MX preference = 10, mail exchanger = aspmx.l.google.com
straightrazorplace.com MX preference = 20, mail exchanger = alt1.aspmx.l.google
.com
straightrazorplace.com MX preference = 20, mail exchanger = alt2.aspmx.l.google
.com
straightrazorplace.com MX preference = 30, mail exchanger = aspmx2.googlemail.c
om
straightrazorplace.com MX preference = 30, mail exchanger = aspmx4.googlemail.c
om
straightrazorplace.com MX preference = 30, mail exchanger = aspmx3.googlemail.c
om