Page MenuHomePhorge

Intermittent DNS issues when attempting to visit we.phorge.it
Closed, ResolvedPublic

Description

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?)

Event Timeline

Matthew triaged this task as High priority.Mar 24 2022, 22:52
Matthew added a project: Phorge Upstream.

Unfortunately this type of issue is in an area that's beyond my network/configuration experience. Is CloudFlare our NS provider?

In T15080#1970, @speck wrote:

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.

In T15080#1970, @speck wrote:

Unfortunately this type of issue is in an area that's beyond my network/configuration experience. Is CloudFlare our NS provider?

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)

Nothing new since last time I commented here.

golyalpha closed this task as Resolved.EditedWed, Sep 21, 06:50
golyalpha claimed this task.

I'm actually gonna close this as Resolved - we can always reopen, or refer back to this, if the issue resurfaces.