How can I troubleshoot DNS caching when a website still shows an old page title ...
How can I troubleshoot DNS caching when a website still shows an old page title after a WordPress update?
I updated the page title and meta description of a WordPress website. The changes were saved successfully in the WordPress admin panel.
However, when I open the website from some browsers or devices, the old page information still appears. On another device, the updated page may appear correctly.
I have already tried:
Clearing the browser cache
Opening the page in Incognito mode
Flushing the local DNS cache
Checking the page source
Testing the URL from another device
I am trying to understand whether this behaviour could be related to local DNS caching, browser caching, or a CDN/server cache.
How can I determine which cache layer is serving the old version of the page? Are there command-line tools such as curl, nslookup, or dig that I can use to identify the source of the cached response?
I would like to troubleshoot the issue before changing the DNS or server configuration.
Top Answer/Comment:
An incognito browser should always show the latest version of a webpage, but doesn't rule out DNS. DNS only is useful for when an IP address changes, and is only a concern if you have a website so large that it has multiple ip addresses, usually in multiple countries etc.
So we can exclude DNS from the search. Given that you tried an incognito browser and it also shows the wrong version of the page, but you sometimes see the correct version of the page, it is the most likely case that this is wordpress caching.
In the admin panel at the top, there should be a button where you can purge the wordpress cache. If you have a caching plugin installed, then the location will be different.
One other thing that could do this is if the webpage is a local intranet site, and you have 2 versions of the webpage. One on the internet, and one for the local intranet. You updated one of the two, and are visiting the other.
In order to rule that out, ping the website from the 2 devices that conflict in the output of the page (one shows the correct version, and one shows the wrong version). If the ip address is different, then that is the problem. Even if one shows an internal ip and the other shows an external ip, then those are already 2 different ip addresses).