How do I properly set DNS for my domain in Route 53?

0

Hello,

I believe all my records are OK but when I run

nslookup -type=NS example.com

(I use my domain name and not example, of course)

I get

DNS request timed out.

timeout was 2 seconds.

Server: UnKnown

Address: 192.168.0.1

DNS request timed out.

timeout was 2 seconds.

DNS request timed out.

timeout was 2 seconds.

I think my NS record is the very same that came by default, I don't think I changed anything.

Record name

example.com

Record type

NS

Value

ns-869.awsdns-44.net.

ns-394.awsdns-49.com.

ns-1429.awsdns-50.org.

ns-1629.awsdns-11.co.uk.

Alias

No

TTL (seconds)

172800

Routing policy

Simple

H
asked 18 days ago149 views
3 Answers
0
Accepted Answer

Your correct name servers are:
ns-1629.awsdns-11.co.uk
ns-1429.awsdns-50.org
ns-394.awsdns-49.com
ns-869.awsdns-44.net

You can tell this by running dig against them -- they respond with NS records. You have changed them to return the incorrect NS records though.

dig @ns-869.awsdns-44.net arculamystica.com -t NS

Change the name server records in the hosted zone to the 4 listed above. (Querying the other 4 name servers there is no response for your domain, so they are not correct.)

Did you register the domain through Route 53?

If yes:
Please go to the Route 53 Console, on the left choose Registered Domains. Select your domain in the main window. You will need to set the name servers to match the 4 listed above

If no (the domain is registered through another registrar):
You will need to login to the registrar where the domain is registered and edit the NS records to match the 4 listed above.

Once you have made the updates, you will have to wait for TTLs to expire before DNS works across the internet. You can create a test record in the zone (something like an A record for test and point to 9.9.9.9) and then run the following to verify it works

dig @ns-869.awsdns-44.net test.arculamystica.com +short

Hope this helps!

profile pictureAWS
EXPERT
iBehr
answered 18 days ago
  • I see records now when querying against one of the name servers. Be patient now for TTLs to time out.

    > dig @ns-1629.awsdns-11.co.uk arculamystica.com
    
    ; <<>> DiG 9.10.6 <<>> @ns-1629.awsdns-11.co.uk arculamystica.com
    ; (2 servers found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21905
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 1
    ;; WARNING: recursion requested but not available
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;arculamystica.com.		IN	A
    
    ;; ANSWER SECTION:
    arculamystica.com.	3600	IN	A	185.199.110.153
    arculamystica.com.	3600	IN	A	185.199.109.153
    arculamystica.com.	3600	IN	A	185.199.111.153
    arculamystica.com.	3600	IN	A	185.199.108.153
    
    ;; AUTHORITY SECTION:
    arculamystica.com.	60	IN	NS	ns-1429.awsdns-50.org.
    arculamystica.com.	60	IN	NS	ns-1629.awsdns-11.co.uk.
    arculamystica.com.	60	IN	NS	ns-394.awsdns-49.com.
    arculamystica.com.	60	IN	NS	ns-869.awsdns-44.net.
    
    ;; Query time: 15 msec
    ;; SERVER: 2600:9000:5306:5d00::1#53(2600:9000:5306:5d00::1)
    ;; WHEN: Tue Jun 04 13:00:55 CDT 2024
    ;; MSG SIZE  rcvd: 247
    
0

Hello.

I checked the NS record for "arculamystica.com" using the "dig" command.
As a result, the name cannot be resolved as shown below.

dig arculamystica.com ns

; <<>> DiG 9.16.1-Ubuntu <<>> arculamystica.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 64409
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 1468 msec
;; SERVER: 2405:6581:bd60:600:9a2d:baff:fe51:9c0#53(2405:6581:bd60:600:9a2d:baff:fe51:9c0)
;; WHEN: 火  6月 04 20:44:30 JST 2024
;; MSG SIZE  rcvd: 46

I also checked the NS record with "whois".
As a result, you can see four records listed in "Name Server".
Does it match the NS record registered in Route53's hosted zone?
If they do not match, try changing the Route53 hosted zone's NS record to match the "whois" result.

whois arculamystica.com
   Domain Name: ARCULAMYSTICA.COM
   Registry Domain ID: 2884189385_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.registrar.amazon.com
   Registrar URL: http://registrar.amazon.com
   Updated Date: 2024-05-24T11:21:13Z
   Creation Date: 2024-05-24T11:11:05Z
   Registry Expiry Date: 2025-05-24T11:11:05Z
   Registrar: Amazon Registrar, Inc.
   Registrar IANA ID: 468
   Registrar Abuse Contact Email: abuse@amazonaws.com
   Registrar Abuse Contact Phone: +1.2024422253
   Domain Status: ok https://icann.org/epp#ok
   Name Server: NS-1101.AWSDNS-09.ORG
   Name Server: NS-1574.AWSDNS-04.CO.UK
   Name Server: NS-508.AWSDNS-63.COM
   Name Server: NS-520.AWSDNS-01.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
profile picture
EXPERT
answered 18 days ago
profile picture
EXPERT
reviewed 18 days ago
  • It may take some time for domain changes to be reflected, so please wait a while before attempting name resolution. By the way, when I checked using the "dig" command, I was able to see the following.

    dig arculamystica.com ns
    
    ; <<>> DiG 9.16.1-Ubuntu <<>> arculamystica.com ns
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29975
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ;; QUESTION SECTION:
    ;arculamystica.com.             IN      NS
    
    ;; ANSWER SECTION:
    arculamystica.com.      60      IN      NS      ns-394.awsdns-49.com.
    arculamystica.com.      60      IN      NS      ns-869.awsdns-44.net.
    arculamystica.com.      60      IN      NS      ns-1429.awsdns-50.org.
    arculamystica.com.      60      IN      NS      ns-1629.awsdns-11.co.uk.
    
    ;; Query time: 130 msec
    ;; SERVER: 192.168.11.1#53(192.168.11.1)
    ;; WHEN: 火  6月 04 23:28:20 JST 2024
    ;; MSG SIZE  rcvd: 183
    
0

Can you give your actual DNS domain name - so that folks here can do some lookup to see if you have configured it correctly.

AWS
EXPERT
answered 18 days 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