server IP address could not be found DNS_PROBE_FINISHED_NXDOMAIN

0

I have already scoured this forum and other web resources. I tried what was suggested to fix this issue and I have not had success. Here is my issue / question?

I have a domain devonacloud.com registered through Route 53. I created a Hosted Zone for this domain. I did not edit any of the records created in the Hosted Zone. I also created an S3 bucket with the same name. I gave this bucket the property of being a static site, I gave it a public access policy, upload a simple html file, and tested the endpoint. The endpoint works as you can see here http://devonacloud.com.s3-website-us-east-1.amazonaws.com/.

Finally, I created an alias record for this domain and chose this bucket for that record. I saved the record. Now, when I try to visit this domain I get the dreaded server IP address could not be found message in chrome.

Various things I tried were to flush my DNS cache. I also tried:

wti@robert-dev:~$ wget devonacloud.com
--2020-04-19 18:13:27--  http://devonacloud.com/
Resolving devonacloud.com (devonacloud.com)... failed: Name or service not known.
wget: unable to resolve host address ‘devonacloud.com’

wti@robert-dev:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.14.30
nameserver 192.168.14.31

wti@robert-dev:~$ dig devonacloud.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> devonacloud.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2721

robert.risk@we-laptop93:~$ nslookup devonacloud.com
;; Got SERVFAIL reply from 192.168.14.30, trying next server
;; Got SERVFAIL reply from 192.168.14.31, trying next server
;; connection timed out; no servers could be reached

I also visited https://www.whatsmydns.net/#NS/devonacloud.com and noticed that the NS records have not fully propagated. I find that strange because I've been dealing with this issue for a few days.

The only off-color thing I can think of is I previously had this domain point to a static IP I configured on a Lightsail instance. I've deleted the static IP and the Lightsail instance, so I'm surprised if this would cause an issue.

When I click on my domain in Route 53, the name servers are:

ns-1196.awsdns-21.org
ns-1701.awsdns-20.co.uk
ns-403.awsdns-50.com
ns-657.awsdns-18.net

And in its Hosted Zone, the values for the NS record set are:

ns-348.awsdns-43.com.
ns-955.awsdns-55.net.
ns-1200.awsdns-22.org.
ns-1950.awsdns-51.co.uk.

Should these be the same? Can anyone see what might be causing the server IP address could not be found error and how to resolve it?

asked 4 years ago1147 views
2 Answers
0
Accepted Answer

Hi,

The nameservers associated with the registrar should be the same as present in the hosted zone, so that correct nameservers are used for resolution.

The correct hosted zone is present with the nameservers:
ns-348.awsdns-43.com.
ns-955.awsdns-55.net.
ns-1200.awsdns-22.org.
ns-1950.awsdns-51.co.uk

as a dig to devonacloud.com using these nameservers gives and IP as seen below:

dig devonacloud.com @ns-348.awsdns-43.com +short
52.216.200.122

These nameservers should be the ones that are present with the registrar. Hence, When you click on your domain in Route 53, the name servers should be :
ns-348.awsdns-43.com.
ns-955.awsdns-55.net.
ns-1200.awsdns-22.org.
ns-1950.awsdns-51.co.uk

Please use the steps mentioned in the following document to add the above-mentioned nameservers associated with the hosted zone to your domain and remove the existing nameservers:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing

Hope this helps. Please write back in case you still face the issue post these steps.

answered 4 years ago
profile picture
EXPERT
reviewed 11 days ago
0

Hi! I'm having the same exact issue with my domain. jennariddle.com.
Thanks in advance!

jriddle
answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions