I moved 9 domains from GoDaddy to hover.com, and all went as normal, except for bits.codecasting.org. It's not working. Having no luck tricking the Internet to find it.
Trying a test with hello.codecasting.org, to see if the problem is with Amazon Route 53, which is where I've moved the DNS from GoDaddy. It should point to this post. Let's see if it works.
Nope. That didn't work.
Then I saw the problem. On Route 53, I had set up codecasting.com, but the domain is codecasting.org. I knew it had to be something like that. :-)
I re-did everything with codecasting.org, told hover.com about the new nameservers.
Now I have to wait until the new nameserver locations make their way around the net, I guess. Because it's still not resolving. Taking a break.
An hour later and it's still not finding bits.codecasting.org on any of my machines, located anywhere.
Going to try using hover.com as the DNS, and have reset the nameservers to ns1.hover.com and ns2.hover.com.
I've mapped buongiorno.codecasting.org to a test node in the world outline here, to see what happens. If it maps then we know that hover's dns is getting the request because this name is not defined on Amazon Route 53.
It doesn't resolve, but that could just be because the nameserver updates haven't percolated yet.
I've moved the DNS for codecasting.org to hover. Now nothing is resolving. All of them are getting errors. I guess I'll wait a while to see what happens with this, and hopefully things will shake out.
Switched the DNS for codecasting.org back to Amazon Route 53.