No DNS record created; app inaccessible

Created an app with fly launch. I think at some point I declined to add an IP when the wizard asked me for that.

Later I assigned an IP with fly ips allocate-v4. Now I have an IP for my app:

fly ip ls                     
VERSION	IP           	TYPE           	REGION	CREATED AT       
v4     	66.241.125.xx	public (shared)	      	Jan 1 0001 00:00

However, dig still returns nothing:

dig elasticsearch-frdm.fly.dev

; <<>> DiG 9.16.48-Ubuntu <<>> elasticsearch-frdm.fly.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40512
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;elasticsearch-frdm.fly.dev.	IN	A

;; Query time: 4 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Nov 06 14:12:09 PST 2024
;; MSG SIZE  rcvd: 55

Also, even if I curl 66.241.125.xx from within this machine, it returns Recv failure: Connection reset by peer.

At the end of fly deploy, I get a DNS warning:

WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
You can fix this by configuring your app to listen on the following addresses:
  - 0.0.0.0:9200
Found these processes inside the machine with open listening sockets:
  PROCESS        | ADDRESSES                              
-----------------*----------------------------------------
  /.fly/hallpass | [fdaa:4:e9ed:a7b:2dbb:d0cb:e271:2]:22  
...
Checking DNS configuration for elasticsearch-frdm.fly.dev:9200
WARN DNS checks failed: expected 1 A records for elasticsearch-frdm.fly.dev:9200., got 0

Don’t know what else to do at this point.

After a while dig started returning the expected 66.241.125.x address.

I changed the [[services.port]] to 80 (it was 9200), which may have something to do with it, since I read elsewhere that nonstandard ports need a dedicated IP, and I had created a shared one.

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