I notice now that the dashboard says the app has no IP address. Was it supposed to create one automatically?
EDIT: indeed, assigning an IP address solved the missing DNS. Why didn’t the documentation instruct me to assign an IP address?
Even after setting an IP address, I somehow was not able to access my running instance of pentacent/keila:latest and when trying to fix it, flyctl asked me to put in my credit card information, which I have no desire to do until I can validate that my use case can work. By for now fly.io
@beeb I don’t understand most of what you just described. I don’t believe the issues you ran into were related to DNS, though.
You should be able to access an app publicly without having to update a credit card form. If you’re up for posting details about what you ran into, I’m sure we can help.
Hey kurt, you are right that it was not in the end a DNS issue for me. It was simply the system not assigning an IP for my app by default, and the instructions in the docs (I followed the dockerfile deployment page) not mentioning this. Even after solving this, my app would somehow still not work, and I wanted to try to redeploy with different environment variables, and this is when it asked me to fill a credit card. I switched to railway.app which worked on the first try.
I think the issue is: we don’t allow deploys of images from Docker Hub without a credit card. It sounds like that might’ve worked once for you, which is interesting. In general, you need a credit card on file to deploy from Docker Hub.
@beeb, fly.io is awesome – you should give it a longer try. This is an unusual outage issue for them. I’m a little surprised they haven’t disabled their DNS servers which seem to be causing intermittent problems for days – but hopefully they can fix it soon.
I’m still seeing the issue this morning, for example three consecutive runs checking Google Public DNS 8.8.8.8 fails for fly.dev (and also our subdomain):
$ host fly.dev 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
fly.dev has address 77.83.140.34
fly.dev has IPv6 address 2a09:8280:1:a270:b8f5:b9f7:8891:f3
$ host fly.dev 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
fly.dev has address 77.83.140.34
Host fly.dev not found: 3(NXDOMAIN)
Host fly.dev not found: 3(NXDOMAIN)
$ host fly.dev 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
Host fly.dev not found: 3(NXDOMAIN)
The problem is that the authoritative nameservers for cdn77.org fail to properly handle ECS(EDNS Client-Subnet) options when they contain an IPv6 client subnet, although they handle IPv4 client subnets just fine.
We’re working on it. This is not obviously a problem with our nameservers. It also takes like 48 hours to get nameservers to propagate, so there’s no quick fix.
We’re trying to ask Google. They happily return a result from each or our name servers in our tests. We never return an nxdomain for an app, so it’s really unclear why that’s happening.
The current theory is that their cache is poisoned from a previous nxdomain error.
@kurt ah yes that explains the credit card, I also switched from a 1-line dockerfile (FROM …) to a line in the config file since my dockerfile was not doing much. I didn’t know one needed a CC and the other didn’t. Anyway, I might give it another go when I get a chance.
Yes, it appears as of this post that resolving via 8.8.8.8 sometimes does not return an AAAA record and sometimes does not return A or AAAA records. When resolving via 2001:4860:4860::8888, it is also still failing intermittently:
# loop running host so we can detect flaky responses
$ while true; do host fly.dev 2001:4860:4860::8888; sleep 0.5; done;
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:
Host fly.dev not found: 3(NXDOMAIN)
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:
Host fly.dev not found: 3(NXDOMAIN)
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:
fly.dev has address 77.83.140.34
fly.dev has IPv6 address 2a09:8280:1:a270:b8f5:b9f7:8891:f3
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:
Host fly.dev not found: 3(NXDOMAIN)
Using domain server:
Name: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Aliases:
fly.dev has address 77.83.140.34
Host fly.dev not found: 3(NXDOMAIN)
Host fly.dev not found: 3(NXDOMAIN)
We did the workaround suggested above where instead of just a CNAME that resolves using the fly.dev nameservers, we put the IPs in our domain, so that’s working to avoid the problem.
I’m sorry, I tried to reply right away to your question but my replies are limited/delayed as a newer user of this forum, even though I’ve had a fly account for awhile…