One week ago, my hosting provider moved to another server and changed the IP address from 18.104.22.168 to 22.214.171.124. Obviously, everything was prepared fine, even the TTL handling.
Okay, I understand that updating the ISP provider’s DNSses worldwide could take up to 24 hours and at the end of the day this cannot be done real time. Yesterday, I tried to call up my domain marco-steinhaeuser.de in several browsers and operating systems and failed with a timeout. Only a few times the page was loading properly. Checking the host of the domain with $
host marco-steinhaeuser.de, sometimes the old IP-address appeared, sometimes the new one. What the hell is going on here?
Linux doesn’t cache the DNS by default, on Windows you had to enter
$ ipconfig /flushdns on your command line to clean your DNS cache. After clearing the router’s DNS cache as well (a simple reboot did it), the same behavior appeared, this way I excluded the problem on my site. Alright, next step:
$ whois marco-steinhaeuser
gives you a clear idea which Domain Name Servers (DNS) are used by the hosting provider and if the IP change was ended up finally at your country’s NIC. The result is:
Which looks nice from my hosting provider’s site. Just let’s go ahead with looking up which entry was made for marco-steinhaeuser.de on the name servers ns1.scunc.it and ns2.scunc.it. First of all, call nslookup on your command line:
Now, “nslookup” the server you want to inspect:
> server ns1.scunc.it
Default server: ns1.scunc.it
> set type=a
> server ns2.scunc.it
Default server: ns2.scunc.it
> set type=a
Alright buddy, that looks okay as well: The entries for the new IP address on both DNSses on your hosting provider’s site seem to be correct. The next step shall be to check your ISP’s name server. You shall find that information at your router as it is entered automatically by default.
In my case (Kabeldeutschland) I had to nslookup 126.96.36.199 as well as it’s alternative 188.8.131.52. Are you still in nslookup mode on your console? Here we go:
> server 184.108.40.206
Default server: 220.127.116.11
> set type=a
Wow! The new IP address is updated at least at the primary name server! But look at this one:
> server 18.104.22.168
Default server: 22.214.171.124
> set type=a
Whatever the “Non-authoritative answer” should mean: Obviously both official Kabeldeutschland DNS servers are not synchronized. That’s a clear server misconfiguration and misbehavior in my opinion. To be honest: How the hell that can happen to a certain ISP?
However, to fix your problem, just turn off the alternative name server in your router.
No probs at all, shit can happen. So I called the 0-800 hotline to tell them what they did wrong. In the moment it was over the head of that 1st line guy and he could not help me seing my cable modem online or whatever, he tried to delegate me to another telephone number with massive costs (95 ct per minute). Unfortunately, he was not able to assign a ticket to a 2nd line. Service looks different, doesn’t it?
Of course, I would never call this hilarious number to tell them _their_ problems. Also, it doesn’t make sense to bother the server owner you would find on ripe.net as he has probably different stuff to do. Instead, I wrote all the details and logs he would need to email@example.com who is the Zone-C of kabeldeutschland.de. Of course, I didn’t get any reply yet, let’s see whether something happens at all…
Many thanks to my mate Thorsten who helped me sorting this out!
Thanks Marco. Your article is still helpful even after 7 years. Going through the similar issue right now. I’ve been going nuts wondering why can’t I point the domain to the new server and it turned out that there are outdated DNS records on Kabel’s side.
Tricky to find out, isn’t it? 🙂
I just wonder that this is still an issue after seven years. Well – might not be the only construction area @Kabeldeutschland ^^