Hello, I have this scenario (for a blog system):
To check it’s availability, a user accesses a subdomain that doesn’t exist so Chrome says DNS_PROBE_FINISHED_NXDOMAIN no IP found.
After that, he creates an account with that subdomain, so the system updates the DNS to add it and the subdomain is accessible, HOWEVER :
- for new users accessing that subdomain, it works directly
- for the initial user, even if he refreshes Chrome, it still says DNS_PROBE_FINISHED_NXDOMAIN!
Actually, even if he accesses it from his phone it still says DNS_PROBE_FINISHED_NXDOMAIN, but if he goes on the phone on the 4G network, it works so it’s not Chrome’s fault but his wifi network keeping its cache.
The question: how can this be overcome so that the subdomain can work for him after it was created without him needing to go to other wifi/4G.
I am using Cloudflare for the DNS so it doesn’t allow wildcard subdomains soI have to create them through a script, however if the domain was accessed before it was created on Cloudflare, it still won’t be accessible on the same network until cache is updated which can take a day?