After successfully moving to a new hoster, I'm having a weird issue on just my computer (Windows 10). After propagation was complete and I removed the temporary entries in my hosts file, it looked fine for about a minute (apparently some sort of local cache), and then it wasn't. Checking nslookup, I saw this strange scenario:
PS C:\Users\Karen> nslookup mail.proverbs2525.org Server: UnKnown Address: 192.168.1.1 Non-authoritative answer: Name: proverbs2525.org Address: 22.214.171.124 Aliases: mail.proverbs2525.org PS C:\Users\Karen> nslookup www.proverbs2525.org Server: UnKnown Address: 192.168.1.1 Non-authoritative answer: Name: proverbs2525.org Address: 126.96.36.199 Aliases: www.proverbs2525.org PS C:\Users\Karen> nslookup proverbs2525.org Server: UnKnown Address: 192.168.1.1 Non-authoritative answer: Name: proverbs2525.org Address: 188.8.131.52
www. were correct, and they even claimed to simply be aliases of the base domain, but a query on the base domain itself pointed to the old server. What???
Then, after a couple hours I noticed that the previously behaving
www. versions had also reverted to the old IP! Then a little later they got well again. Then after an hour or so away from my computer I checked again, and
www. is correct, but
mail. (and of course the naked domain) were wrong. A few minutes after that, they swapped (
mail. was correct but
www. was wrong). I'm going mad!
The naked domain doesn't come and go, but is consistently wrong. Re-adding the hosts entry
184.108.40.206 proverbs2525.org fixes it, but when I remove the hosts entry again the naked domain goes back to 220.127.116.11, possibly taking the subdomains with it. It's as if I have some secondary, hidden hosts file (shall I call it a "ghosts file"?) that still has 18.104.22.168 in it and wants to assert itself when I'm not looking. I moved two other domains at the same time, and they are working fine. It's definitely not a propagation problem - I set all the TTLs to 10 minutes the previous day, and it has been about 8 hours since I changed the nameserver entries. My husband's computer on the same LAN, my phone, geopeeker, etc. all see everything pointing to 22.214.171.124 as they should. Can someone help me find the ghost?