Cannot init consul - server misbehaving

[timothym]

Deployments and health checks have started to consistently fail for one of my apps (starting just today)

ERROR: cannot init consul: cannot connect to consul: register node "***********-z4k69dz36x0qp5mx/litefs": Put "https://consul-iad-12.fly-shared.net/v1/catalog/register": dial tcp: lookup consul-iad-12.fly-shared.net on [fdaa::3]:53: server misbehaving

and then eventually:

machine has reached its max restart count of 10

I’ve attempted fly consul detach/attach to reset the consul secret and tried disabling the health checks in an attempt to get a deployment working, but nothing I’ve tried so far has fixed the above issue. Is there anything in particular I can do to resolve this?

[savikko]

I confirm also that I am getting same issue:

305780EF3D985F0B: cannot acquire lease or find primary, retrying: fetch primary url: Get "https://consul-fra-6.fly-shared.net/v1/kv/<redacted>/litefs/<redacted>": dial tcp: lookup consul-fra-6.fly-shared.net on [fdaa:0:<redacted>::3]:53: server misbehaving

[lillian]

the DNS server for this domain is broken, I’ll look into it shortly.

[timothym]

Thanks @lillian for looking into this!

Would this qualify as an incident? It would be helpful to know the status of this issue so I know when it’s resolved. The issue is currently blocking me from deploying my app.

[roadmr]

@timothym we’ve [started an incident](Fly.io Status - Name resolution for Fly Consul cluster degraded) for this issue, in case you want to track it!

• Daniel

[roadmr]

This should now be fixed.

[savikko]

Seems to be working, thanks!

[timothym]

Working for me as well, thanks for looking into this and fixing it!