This happens when trying to read https://storiesonline.net/n/34081/from-the-top/43 on my mobile phone.
I use Firefox on my phone and a variation thereof on my desktop PC. Reading the chapter on my PC works just fine, trying to read it on the smartphone does not.
I had a look at the previous chapter on my phone and that worked just fine, I had a look at the newest chapter of another story (posted yesterday) and that also worked just as it should.
The old servers had something called IPv6 addresses for mobile stuff.
The new hosting solution doesn't have IPv6 yet.
I deleted the addresses for mobile stuff, and phones should automatically switch to the old IPv4 protocol.
It seems your phone is caching the DNS info for the old servers.
I don't know how to fix it on your phone. My iPhone works fine with the new server.
The new hosting solution doesn't have IPv6 yet.
Seriously? 🤦🏼♂️ It's 2025.
Give the man a break - he is still in the process of moving between boxes. Having done that a few times myself I remember all the little fiddly bits that have to be prioritized. Something always has to be the last thing done.
Give the man a break - he is still in the process of moving between boxes. Having done that a few times myself I remember all the little fiddly bits that have to be prioritized. Something always has to be the last thing done.
That waa NOT a criticism of Lazeez, but of an ISP which does not support IPv6.
I didn't take it to mean Lazeez hadn't implemented it, but that the ISP did not offer it, and in 2025 that's just not acceptable.
I have seen it take over 24 hours for DNS servers to update info. Your phone uses a different DNS server than your desktop.
I have seen it take over 24 hours for DNS servers to update info. Your phone uses a different DNS server than your desktop.
The publisher of the DNS records can set the caching time. When I'm going to move an IP, I set the value very low (as in minutes) for a few days beforehand. It puts a bit of extra load on my DNS servers, but that's a small price to pay to avoid caching problems. Once the new addresses are deployed, I set the value back to normal.
The main factor is how frequently the DNS server that your ISP uses gets updated. Some are done about once a day.
The main factor is how frequently the DNS server that your ISP uses gets updated. Some are done about once a day.
But if it returns an error or a Not found response, shouldn't that cause it to update then?
The main factor is how frequently the DNS server that your ISP uses gets updated. Some are done about once a day.
No, the main factor is the configuration settings for the DNS zone, specifically the 'refresh', 'retry', 'expire', and 'minimum' values for a specific zone. Even if a DNS server is reloaded, servers that have cached the address will not ask again until the time specified for 'expire' has passed. For stable sites that can be a week or more. On my main server, it's two weeks.
Restarting named has zero effect on querying servers. The authoritative DNS servers will have the correct information, but if a querying server (or your PC/Mac/phone/tablet) has a non-expired DNS record cached, it'll use that and not ask the authoritative servers.
I don't know if it's related, but last night I had some odd server not found errors, and it wasn't just SOL.
I had to reboot my PC and power cycle my home gateway to fix it. It has been stable since.