DNS_PROBE_FINISHED_NXDOMAIN with S3 bucket

Question

(My previous solution based on the EC2 instance stopped working with DNS_PROBE_FINISHED_NXDOMAIN error and I made the decision to switch to static hosting in the S3)

**My domain**: oriongamingworld.net
**Region**: Frankfurt

I followed the instructions from the AWS documentation regarding the hosting of static sites.

So I created two buckets and configured them as described in the documentation. Copied static files inside and made configurations. Public addresses are working well from the bucket:

http://oriongamingworld.net.s3-website.eu-central-1.amazonaws.com/

Next, I deleted the previously created hosted zone in Route53 and recreated it from scratch. I followed the guide and made two additional A records with proper names: oriongamingworld.net, www.oriongamingworld.net

In the end, I still have this issue with DNS_PROBE_FINISHED_NXDOMAIN in the browser when I'm trying to open:

http://www.oriongamingworld.net/

- I tried different devices - it is the same everywhere
- I checked NS names - they are the same as I am getting from Whois.

Andrew M · Answer

I found the root: my domain was suspended since I didn't confirm the verification email. So I resend it and now my config looks like:

![My domain data inside AWS](/media/postImages/original/IMWnIdYauiRcq5CWEbQx9sPg)

and that is info from whois:

![WHOIS info](/media/postImages/original/IMCKn_QpF2TuyIq9rY2IXbIQ)

Inside the account, it was unsuspended after I resend and confirmed my email address. NS are identical in both cases, but on the internet it still has DNS_PROBE_FINISHED_NXDOMAIN. Maybe it needs more time, I'll wait for a while.

Riku_Kobayashi · Answer

Hello.

Are domain zones managed by Route53?
I checked the NS record with the command below, but it was not a Route53 NS record.
If you are managing with Route53, you will need to copy the Route53 NS record and register it again in the NS record of the zone you are managing.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingNewSubdomain.html#UpdateDNSParentDomain

dig oriongamingworld.net ns

; <<>> DiG 9.16.1-Ubuntu <<>> oriongamingworld.net ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33548
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;oriongamingworld.net.          IN      NS

;; AUTHORITY SECTION:
net.                    900     IN      SOA     a.gtld-servers.net. nstld.verisign-grs.com. 1695744377 1800 900 604800 86400

;; Query time: 46 msec
;; SERVER: 192.168.11.1#53(192.168.11.1)
;; WHEN: Wed Sep 27 01:06:27 JST 2023
;; MSG SIZE  rcvd: 122

DNS_PROBE_FINISHED_NXDOMAIN with S3 bucket

Relevant content