| golyalpha | |
| Mar 24 2022, 18:19 |
| F186596: image.png | |
| Oct 6 2022, 09:22 |
| F186594: image.png | |
| Oct 6 2022, 09:22 |
I don't know if this is specific to me, but, occasionally the we.phorge.it domain name refuses to resolve. I'm using CloudFlare DNS as my DNS server, and usually it does resolve properly after a few attempts (after which the answer is cached, so the issue only resurfaces after TTL is reached, if at all).
Might be worth it at least monitoring the nameservers in use for uptime, and potentially switching NS providers (maybe even using CloudFlare in the Free tier?)
Unfortunately this type of issue is in an area that's beyond my network/configuration experience. Is CloudFlare our NS provider?
I think in this case, golyalpha is referring to https://1.1.1.1/dns/ - which I also use for my Pi Hole but I haven't seen this issue.
The NS provider for Phorge is probably Gandi - at least they're the registrar for the domain.
Edit:
It is Gandi.
phorge.it SOA 1800 ns1.gandi.net hostmaster@gandi.net 1626090333 10800 3600 604800 10800 phorge.it NS 10800 ns-119-b.gandi.net phorge.it NS 10800 ns-245-a.gandi.net phorge.it NS 10800 ns-92-c.gandi.net
But the TTL is extremely short (10mins):
we.phorge.it A 600 198.74.57.92
I would suggest increasing the TTL to a day if you are not planning on moving servers in the near future.
I mean, that's not a particularly good solution to the problem. It just makes the time for which it appears to be fixed longer (even though nothing has changed)
That being said, I haven't had this issue in a while, so it might've been Gandi had been doing some maintenance or something. (or something else changed, I haven't checked)
I'm actually gonna close this as Resolved - we can always reopen, or refer back to this, if the issue resurfaces.
I setup a cron that makes a bunch of DNS queries for different records within the phorge.it zone from all the authoritative nameservers for the zone (see T15080#1985).
So far I'm getting occasional spikes in DNS resolution times on Gandi's end:
Good to know that somebody is monitoring this problem. Feel free to reopen when somebody can share more details
Seems to be gone for now, the only time I get increased lookup times or complete fails is when there's high internet traffic on my own network. Might've just been some of us got unlucky.
Also, @Cigaryno, DNS_PROBE_STARTED is a fully client-side error, nothing we can do about that.