[ad_1]
I modified DNS to the brand new server’s IP 2 weeks in the past.
(from 123.123.123.123 to 234.234.234.234)
I’ve verified that the DNS TTL has expired and I believe the DNS propagation is full.
I checked that the DNS cache of the ISP was additionally up to date.
;; ANSWER SECTION:
completely satisfied.newyear.com. 254 IN A 234.234.234.234
Nevertheless, even after two weeks, about 0.01% of the full requests are making calls to the IP of the outdated server by the area.
Once I extract the decision host from the Nginx log in my outdated server, I can see that the purchasers name utilizing my area completely satisfied.newyear.com.
xxx.xxx.xxx.xxx - - [02/JAN/2022:10:55:47] "POST /completely satisfied/new/12 months HTTP/1.1" 200 2 "-" "Dalvik/2.1.0 (Linux; U; Android 11; SM-G996N Construct/RP1A.200720.012)" 0.019 "0.005" 443 completely satisfied.newyear.com
My server receives calls from varied smartphones and net purchasers, and I can not shut down my outdated server so long as the decision comes into the outdated server.
(because the goal of the DNS change was to close down the outdated server, I have to transfer all incoming shopper requests to the brand new server.)
My guess is there’s an issue with the cache on the shopper system facet, is there any resolution?
Is it attainable that the shopper system’s dns cache would not expire for two weeks?
If not a shopper downside, what’s the issue?
[ad_2]
