|February 16th, 2021|
I'm helping my dad migrate some code to a new server. It was at
220.127.116.11 for years, but ten days ago he changed
his DNS settings to point to
looks good to me:
$ dig notes.billingadvantage.com notes.billingadvantage.com. 1800 IN A 18.104.22.168The TTL is 1800s, or 30min, which agrees with dns.google. I expected everyone would be moved over within a couple hours, but a week later the old server is still receiving traffic nearly as much as the new:
|date||old server||new server|
The old server getting no traffic on the 13th and 14th is probably because that's the weekend, and the users who happen to be still stuck on the old site aren't using it on the weekend. I asked one of the users still getting the old server to try rebooting, to no effect.
I thought maybe something was misconfigured with the name servers, but it looks fine:
$ whois billingadvantage.com \ | grep 'Name Server' Name Server: NS1.ZEROLAG.COM Name Server: NS2.ZEROLAG.COM $ dig notes.billingadvantage.com \ @ns1.zerolag.com notes.billingadvantage.com. 1800 IN A 22.214.171.124 $ dig notes.billingadvantage.com \ @ns2.zerolag.com notes.billingadvantage.com. 1800 IN A 126.96.36.199I'm not seeing any references to the old IP address anywhere.
Any guesses about why the traffic isn't moving over?