Issue finding AAAA records during deployment

Questions / Help
1

During deployment the deployment works right but then fails with this after they are healthy and old ones are torn down.

Deployment Complete
Checking DNS configuration for polar-develop.fly.dev
Error: expected 1 AAAA records for polar-develop.fly.dev., got 0

Happened on 2 apps, both of which has a private IPv6 assigned to them. (deployments have been working up until today)

1 Like
2

I’ve noticed a similar issue. It just started happening this morning. Yesterday there was no issue.

My error:

✔ Machine 908001db169578 [app] update succeeded
Checking DNS configuration for matchhaus-staging.fly.dev
Error: expected 2 AAAA records for matchhaus-staging.fly.dev., got 1

It seems it’s expecting 2 AAAA records for my app; it does seem to have 2 ipv6 addresses assigned though so that makes sense

3

This is an issue due to a bug I introduced, I fully apologise. I pushed out a bug fix which should by in flyctl v0.1.146.

1 Like
4

I see. The DNS check added to flyctl 0.1.144 is counting the total number of ipv6 addresses allocated to the app rather than just the public ones. Private addresses are obviously not present on the DNS records for the domain.

Any idea when 146 will be released?

5

Yep it was pretty silly. 146 should be out now

1 Like
6

Thank you @billy!

7

Hello. I’m still having this issue with the latest flyctl. Did the fix also apply to the darwin/arm64 build? This wasn’t happening for me a few days ago.

$ fly deploy --config fly.staging.toml
Checking DNS configuration for cg-server-staging.fly.dev
Error: expected 1 AAAA records for cg-server-staging.fly.dev., got 0

$ fly version
fly v0.1.146 darwin/arm64 Commit: 81fceeabde42511cf2a585e068fe8e415322657c BuildDate: 2024-01-25T14:33:07Z

Thanks

Edit: Downloading and running v0.1.143, it deployed successfully, so it does seem like a version-related issue.

8

Hi harkinian,
Running dig AAAA cg-server-staging.fly.dev, it looks like there should actually be an IPv6 address attached to your app. Could you confirm that?

9

Huh, for some reason my dig doesn’t show AAAA records for this, but online dig UIs do have it. Probably something on my end. The app settings page does show an IPv6 address, as well as an IPv4. Also, I don’t have ipv6 at home, but that shouldn’t matter for AAAA lookups.

dig AAAA cg-server-staging.fly.dev

; <<>> DiG 9.10.6 <<>> AAAA cg-server-staging.fly.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21914
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cg-server-staging.fly.dev.	IN	AAAA

;; Query time: 0 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Jan 26 18:43:11 PST 2024
;; MSG SIZE  rcvd: 43
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.