DNS Woes
Last month I upgraded to a more powerful server. This migration also managed to carry the domain that houses my DNS servers. So obviously I had to make a change, because even though the servers are with the same company, they're not on the same subnets. anyway....
So, first things first... Go to enom where I have all my domains as a reseller. change the status of the two name servers that are moving. in changing the status, I change it to the IPs of the NEW server.
Of course I also change and add the NS records accordingly.
Sounds ok. Right? Nope. about once a week I see a flipflop. The problem I believe is stemming from network solutions. I use to have this domain hosted with them. around 6 months ago I moved it to enom. but this is the only frickin thing I can think. Since I moved the domain away from them, they have old data and are ignoring the TTL info.
Do this and some of you will see what I'm talking about.
ping ns1.e-places.net
Some will get 66.135.33.70 (this is the OLD ip)
Some will get 69.44.56.158 (this is correct)
Now, even more screwy than that. Because of this crap I have had to keep both the old server AND the new one. however, there are still many times a subdomain won't resolve, even though the information is on BOTH DNS servers.
eg: ping secure.e-places.net
Some of you will get 'host not found'.
I went through and replaced every single record in the old server to point EVERYTHING to the new machine. I also gathered all of the data from the old server to the new by making the new server a slave to the old, and grabbed the zone info.
Anyone got ANY suggestions how to fix this? I'm losing customers a LOT right now, and I don't blame them for leaving.
