6pn.dev/ns1(-4).flydns.io DNS issue? (possible wireguard impact)

1

Is there currently a Fly/6pn.dev DNS issue (e.g. flydns.io expiring)?

If there is(?), this may increase (external>fly) wireguard failures by virtue of failure to resolve the wireguard gateways.

1 Like
2

I also have this problem, does generating new Wireguard configurations solve the issue?

** server can't find cdg1.gateway.6pn.dev: SERVFAIL

3

We are now aware of this and are resolving the issue.

1 Like
4

If fly posted the IPs in this thread - you could manually edit your wireguard config(s) with the IP of the gateway(s) you’re using.

If there is a flydns.io problem, with the associated impact on 6pn.dev, I doubt generating new wireguard configs via flyctl will help. Unless the flyctl wireguard config generator is changed to output IPs (or alternative/working FQDNs) for the gateways.

5

Thank you.
For now we bypassed the problem by replacing the host with the actual endpoint IP

In this case, cdg1.gateway.6pn.dev was 176.58.90.244

6

This should now be resolved. We’re monitoring the situation.

7

Thank you, it is working again here