DNS Probe issue

I am experiemnting with fly recently and have created my app and added my domain to it, yet I got a n issue with: DNS_PROBE_FINISHED_NXDOMAIN I am getting it always on my domain even if my APP is running.

What I did was following the instructions at the fly for adding the records, but that did not work.

You are creating a certificate for xxxxxxxxxxxx.com
We are using lets_encrypt for this certificate.

You can direct traffic to xxxxxxxxxxxx.com by:

1: Adding an A record to your DNS service which reads

A @ XX.XX.XX.XX

You can validate your ownership of xxxxxxxxxxxx.com by:

2: Adding an AAAA record to your DNS service which reads:

AAAA @ XXXX:XXXX:X::X:XXXX

Is there a solution for this?

I am using namecheap as domain provider. I have read the previous answers as well but it did not help me.

Hey There,

The DNS_PROBE_FINISHED_NXDOMAIN error is fairly generic but it is common if the DNS is not configured correctly.

Just to remember, the A record is for your IPV4 address and the AAA is for your IPV6 address.

Also check if there are no conflicting entries with the same host (for example, an A record you might have your newly created pointing to your instance IPV4 address but there is an existing CNAME with the same host but configured to another address).

This tutorial has also an example setting up an A and an AAA record with namecheap.

And this Namecheap article has a tutorial with some potential problems to watch for.

I followed both solutions without luck! I did what it’s written there as well.
I am not sure why but it is not stable. At first it worked at incognito then it stopped working.

Try running:

dig a example.com

And

dig aaaa example.com

You should see the same responses from those as you see from:

dig a <app>.fly.dev
dig aaaa <app>.fly.dev
1 Like

@kurt Igot the same result, but the one I did with .fly.dev gave me an extra authority section!
is that related?

Hey,

Can you please post the results of the commands?

From what you described, it seems like the address is resolving correctly if they are resolving to the same ip addresses. I think that the Authority section should correct. Although I am not sure, I think that fly.dev would be the authoritative name server.

And, if it worked for a while in incognito mode and it stopped, there could be some caching issues as well. I read that this can also happen with DNS_PROBE_FINISHED_NXDOMAIN

Another thing to try then is to change your DNS configuration. At least for testing purposes, can you try to change your local DNS config to another public DNS server such as 8.8.8.8 or 8.8.4.4 (Google).

In summary:

  • please post the results of the dig commands
  • try to change DNS servers in your local machine

The Domain dig a:

dig a hadithtech.com

; <<>> DiG 9.16.1-Ubuntu <<>> a hadithtech.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19842
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: daffe07e564232e6c1b58f816405fcb797100e98a2c5cbd6 (good)
;; QUESTION SECTION:
;hadithtech.com.                        IN      A

;; ANSWER SECTION:
hadithtech.com.         1781    IN      A       66.241.125.178

;; Query time: 10 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:46:15 +03 2023
;; MSG SIZE  rcvd: 87

dig a ghost app:

 dig a https://ghost-hadithtech.fly.dev/

; <<>> DiG 9.16.1-Ubuntu <<>> a https://ghost-hadithtech.fly.dev/
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4497
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: b21a643b7aa5f074f1125ec36405fcde0600f352ada0da5b (good)
;; QUESTION SECTION:
;https://ghost-hadithtech.fly.dev/. IN  A

;; AUTHORITY SECTION:
.                       10800   IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2023030600 1800 900 604800 86400

;; Query time: 20 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:46:53 +03 2023
;; MSG SIZE  rcvd: 165

dig aaa:

Domain

dig aaa https://www.hadithtech.com/

; <<>> DiG 9.16.1-Ubuntu <<>> aaa https://www.hadithtech.com/
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38233
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: d267477833189d4d020bff776405fd2c2bb55421cb4dffd4 (good)
;; QUESTION SECTION:
;aaa.                           IN      A

;; AUTHORITY SECTION:
aaa.                    887     IN      SOA     ns1.dns.nic.aaa. admin.tldns.godaddy. 1678048622 1800 300 604800 1800

;; Query time: 10 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:48:12 +03 2023
;; MSG SIZE  rcvd: 127

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64061
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: d267477833189d4d7dcc5d596405fd2cbc73b8ea677f8d6a (good)
;; QUESTION SECTION:
;https://www.hadithtech.com/.   IN      A

;; AUTHORITY SECTION:
.                       10800   IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2023030600 1800 900 604800 86400

;; Query time: 20 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:48:12 +03 2023
;; MSG SIZE  rcvd: 159

dig aaa fly:

dig aaa ghost-hadithtech.fly.dev

; <<>> DiG 9.16.1-Ubuntu <<>> aaa ghost-hadithtech.fly.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9017
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: fcb5e26ac9cf786aa00595e06405fd36bfb56904809d6611 (good)
;; QUESTION SECTION:
;aaa.                           IN      A

;; AUTHORITY SECTION:
aaa.                    877     IN      SOA     ns1.dns.nic.aaa. admin.tldns.godaddy. 1678048622 1800 300 604800 1800

;; Query time: 10 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:48:22 +03 2023
;; MSG SIZE  rcvd: 127

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42941
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: fcb5e26ac9cf786a223832d86405fd3667bd8fd026453f90 (good)
;; QUESTION SECTION:
;ghost-hadithtech.fly.dev.      IN      A

;; ANSWER SECTION:
ghost-hadithtech.fly.dev. 300   IN      A       66.241.125.178

;; Query time: 100 msec
;; SERVER: 46.197.15.60#53(46.197.15.60)
;; WHEN: Mon Mar 06 17:48:22 +03 2023
;; MSG SIZE  rcvd: 97

I do not have the app running locally.

In just a weird way it worked today, I did not change anything in the settings neither in the namecheap dashboard! Hopefully it will stay up now on!

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