Dns_probe_finished_nxdomain

Support
1

i have api on digital ocean and static site on Netlify. It has been reflected in my dns settings. I constantly receive the same error DNS_PROBE_FINISHED_NXDOMAIN

my dns settings hosted on netlify Netlify App (assuming it won’t be visible to everyone, but hoping it would be visible to admins)

through a dig I see that nameservers from Netlify serving my domain


; <<>> DiG 9.10.6 <<>> +trace [trkohler.com](http://trkohler.com/)
;; global options: +cmd
. 38111 IN NS [i.root-servers.net](http://i.root-servers.net/).
. 38111 IN NS [m.root-servers.net](http://m.root-servers.net/).
. 38111 IN NS [h.root-servers.net](http://h.root-servers.net/).
. 38111 IN NS [c.root-servers.net](http://c.root-servers.net/).
. 38111 IN NS [k.root-servers.net](http://k.root-servers.net/).
. 38111 IN NS [f.root-servers.net](http://f.root-servers.net/).
. 38111 IN NS [g.root-servers.net](http://g.root-servers.net/).
. 38111 IN NS [j.root-servers.net](http://j.root-servers.net/).
. 38111 IN NS [e.root-servers.net](http://e.root-servers.net/).
. 38111 IN NS [l.root-servers.net](http://l.root-servers.net/).
. 38111 IN NS [d.root-servers.net](http://d.root-servers.net/).
. 38111 IN NS [a.root-servers.net](http://a.root-servers.net/).
. 38111 IN NS [b.root-servers.net](http://b.root-servers.net/).
. 38111 IN RRSIG NS 8 0 518400 20221125050000 20221112040000 18733 . Ci7E4nF2OhS7Yc7yI648Eh2su3NnCIGmC1Dutt0NbOquQsTSG7tem0Ue o0V+vIwfG3Mq1tF6gfGwxTRlBbx0gIVq8p+SbMuvt3D8rTpclDvRz5aS TqkOoXZyJR2erDPLn/r8nqQeLo3I5YK/s8bnmU0PSXI8JFFddftJYyI5 Ylr9andfMoAb0W4iBvZecMg9JvoHDio+uT6krg5q1DHL0yRm31FBG8EJ qKUMjOGhGQu36+HUYAQLAvyy6O+1TLYlrXFnGxFX/KA227G1xr1ylsoE cgiINc9IZE4PuRe6YOgEzVTfIzk3Se0TvV0HFlj5UTqCgKeGvvlAvdzs 1Mo4eg==
;; Received 1097 bytes from 2a02:8109:a180:1d8c:52a5:dcff:fed1:3f6f#53(2a02:8109:a180:1d8c:52a5:dcff:fed1:3f6f) in 76 ms

com. 172800 IN NS [a.gtld-servers.net](http://a.gtld-servers.net/).
com. 172800 IN NS [b.gtld-servers.net](http://b.gtld-servers.net/).
com. 172800 IN NS [c.gtld-servers.net](http://c.gtld-servers.net/).
com. 172800 IN NS [d.gtld-servers.net](http://d.gtld-servers.net/).
com. 172800 IN NS [e.gtld-servers.net](http://e.gtld-servers.net/).
com. 172800 IN NS [f.gtld-servers.net](http://f.gtld-servers.net/).
com. 172800 IN NS [g.gtld-servers.net](http://g.gtld-servers.net/).
com. 172800 IN NS [h.gtld-servers.net](http://h.gtld-servers.net/).
com. 172800 IN NS [i.gtld-servers.net](http://i.gtld-servers.net/).
com. 172800 IN NS [j.gtld-servers.net](http://j.gtld-servers.net/).
com. 172800 IN NS [k.gtld-servers.net](http://k.gtld-servers.net/).
com. 172800 IN NS [l.gtld-servers.net](http://l.gtld-servers.net/).
com. 172800 IN NS [m.gtld-servers.net](http://m.gtld-servers.net/).
com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com. 86400 IN RRSIG DS 8 1 86400 20221125050000 20221112040000 18733 . I5it4epK25laf74ZFhYWR/3wGGjsFroYCirdzIyMrzs4vJMU0XLVs+Ws veV+vnXqmVuN5HkJJwcR5Ff43mCZ+KhypfArYQ/RNtGazBKz0gX5wxZ6 2ub1SVr3318yAMtl3iN2N44RB6ZBiEKlur0heBFoBFqW8LpR7/89PqYV lHOTKZGDKGCNZedLPa+ukQcgp2YRdXOZFV3kNgXeKGlxYfK9Nv8eVqnP Tc5bQY1DlZvU026MB9SJG4lY0v4AXPt0gu0iyenC50RTIdVbiq/R2PHj hn92tvVzOZkmyWvchHTP5uvyRAm/ktkqQL+R6i9B+/fqIdyuEw2YEgZI ktNOhw==
;; Received 1172 bytes from 2001:500:a8::e#53([e.root-servers.net](http://e.root-servers.net/)) in 20 ms

[trkohler.com](http://trkohler.com/). 172800 IN NS [ns1.digitalocean.com](http://ns1.digitalocean.com/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [ns2.digitalocean.com](http://ns2.digitalocean.com/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [ns3.digitalocean.com](http://ns3.digitalocean.com/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [dns1.p03.nsone.net](http://dns1.p03.nsone.net/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [dns2.p03.nsone.net](http://dns2.p03.nsone.net/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [dns3.p03.nsone.net](http://dns3.p03.nsone.net/).
[trkohler.com](http://trkohler.com/). 172800 IN NS [dns4.p03.nsone.net](http://dns4.p03.nsone.net/).
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q2D6NI4I7EQH8NA30NS61O48UL8G5 NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20221119052449 20221112041449 53929 com. hYUTcpX5l7kJAr78hLqD/FuTq2H6w3My4YrnqfpuOkpuv3n4r5aLG63b vo3cRytvqc2usP+YMVpPDRkzPbGbOJZL0M6R2U8w0oQPcSstUL27jjJ7 xgInCLHW1iRj4NlGFay8pE5Fw3Rz9P65s0AXX0QEeQ6VwKZmW9MXDlp/ H14cc7l2zzG6ZXrHUNJwzid1r6kONuadYYxYA58dLPdq5g==
O77B2F9OVP208CLPJ3J3FB5QIQE0LDQC.com. 86400 IN NSEC3 1 1 0 - O77BQ3PAP7UN367NNB5O2B3PI7LTRQGN NS DS RRSIG
O77B2F9OVP208CLPJ3J3FB5QIQE0LDQC.com. 86400 IN RRSIG NSEC3 8 2 86400 20221119055206 20221112044206 53929 com. doaKKh2Z02s/nYip4HXk6ijk1lHhKK8GSzsGGjAib5+vbpxnwfYawrOn b4xsynNuqjDgpPj6CUH+SRiR+hyxymNEOjFXfJCHlVsf/eWlUXBFdIuZ 2J+vZB4EPt+zNvhNlJOcc3on7si59jXUbCuzmwKo+7Rhj77Kd24bs30P xBF5bD8eSMGWldngWWr0vy9QWvtGw+HIWzd0AyAMnuIi3Q==
;; Received 878 bytes from 2001:502:8cc::30#53([h.gtld-servers.net](http://h.gtld-servers.net/)) in 26 ms

[trkohler.com](http://trkohler.com/). 20 IN A 34.159.58.69
[trkohler.com](http://trkohler.com/). 20 IN A 18.192.76.182
;; Received 73 bytes from 2620:4d:4000:6259:7:3:0:1#53([dns1.p03.nsone.net](http://dns1.p03.nsone.net/)) in 29 ms

however if i try to have a response from the ip address there is an error when I try to curl one of that ip curl 34.159.58.69 -v

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 34.159.58.69:80...
* Connected to 34.159.58.69 (34.159.58.69) port 80 ([#0](https://netlify.zendesk.com/tickets/0))
> GET / HTTP/1.1
> Host: 34.159.58.69
> User-Agent: curl/7.79.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Server: Netlify
< X-Nf-Request-Id: 01GHNE7KD6786ZDMMWDNT7K01W
< Date: Sat, 12 Nov 2022 08:10:25 GMT
< Content-Length: 0
<
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
* Connection [#0](https://netlify.zendesk.com/tickets/0) to host 34.159.58.69 left intact

how I can ensure that netlify would serve requests to my domain name reliably?

2

Direct curl of IP address wouldn’t work as multiple domains are being routed via the same IP address.

You may want to check your nameserver configuration.

Currently, it seems that you have both DigitalOcean and Netlify DNS there:

If you check my dig result below, you’ll see that the Netlify DNS’s nameservers returns a correct response for your domain, but not DigitalOcean’s nameservers:

image
image703×98 3.75 KB

Chances are your browser connects to the DigitalOcean’s nameservers, see that there are no A records there and return a DNS_PROBE_FINISHED_NXDOMAIN.

I would recommend you to just remove DigitalOcean’s nameservers from your NameCheap panel and left the Netlify DNS’s there. You will then want to add the IP address for your API server to the appropriate subdomain in Netlify DNS.

1 Like
3

thank you very much! it worked out!