Posted by Daljit of NORN on January 20th, 2010 filed in Diagnostic Reports, Enraged Owlbear


So I’ve been waiting for a particular domain to propagate through the net’s DNS servers. I thought to myself “Man, this is taking a while. You know, this may be taking a bit too long.” So I thought, let me try switching to a DNS server other than the one my ISP uses. I tried Google’s Public DNS ( and in case you’re interested) and it didn’t resolve there either. Curiouser and curiouser. Did a name server lookup (in windows command prompt: nslookup -debug yourdomain.com) and found that oh look, the DNS records are actually point to Dreamhost like they’re supposed to. So what gives? What’s going on? I think something curled up and died on Dreamhost’s end when I tried to set up the full hosting for the domain. I’m going to park the domain, and then set it back to full hosting to see if I can’t get it unstuck. Surely my cunning plan cannot fail!

If it does fail, I’ll just e-mail tech support because I don’t know if I’ll be able to kick start things at my end. Curse you server errors! You’ve cost me valuable time in which I could have been hilarious!

Comments are closed.