DNS resolution failing after creating dedicated ip addresses

[gilozoaire]

Hello, I recently created dedicated ipv4 and 6 ip addresses and despite having waited 30+ mins, the dns is still not reachable.

I’ve configured static ips via flyctl ips allocate-v4 --region ams ..., they are correctly showing in the UI

Despite this, they are not reachable when I check https://dnschecker.org/. They are not reachable when opening the domain in the browser, or reachable via our apps. In short, it doesn’t look the ip addresses are being propagated.

If I then allocate a shared address via --shared, then the dns starts being resolved. is this a normal ocurence?

How long do I need to wait before the new ip starts being resolved by dns servers?

Edit:
If I remove the --region aws param, then it 's starting to get propagated and available through dns lookup… quite strange

Edit #2:
After waiting for a long time, only the shared ip (US based) is available:

[lillian]

regional IPs are not returned in .fly.dev queries. you can allocate a global IP (without --region flag) to do what you want.

note that shared IPs aren’t based in US, rather they are routed to the region nearest to the user, with anycast.