- Newest
- Most votes
- Most comments
Hello. To properly configure your public hosted zone, verify the following settings:
- The public hosted zone is populated with the appropriate resource record sets.
- Your non-AWS domain name registrar points to the name servers in your Route 53 public hosted zone.
Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you're using the most recent AWS CLI version.
Confirm that you're using the appropriate resource record sets
Confirm that you created the appropriate resource record set. For more information, see Values that you specify when you create or edit Amazon Route 53 resource records and Values specific for simple records.
Confirm that your non-AWS domain name registrar points to the name servers in your Route 53 public hosted zone
You can use Route 53 for DNS services and another domain name registrar for domain registration. In this case, your domain name registrar must reference the name servers in your Route 53 public hosted zone. To do this, query an internet-based whois utility to take the following steps:
- Find the registrar for your domain name. Enter your domain name in the query field, select the Domain option, and then choose Submit. The query results include the domain name registrar and the authoritative name servers for the domain name. Note: The query results might return a list of name servers other than the name servers that are associated with your Route 53 public hosted zone. To update the list of name servers that are associated with your domain name, contact your domain name registrar.
- Find contact information for your domain registrar. Enter the name of the registrar in the query field, select the Registrar option, and then choose Submit. Use this information to contact your domain registrar. Ask your domain registrar to update the list of name servers, so your domain name can reference them in its public hosted zone.
- Verify that the DNS service that you're transferring from doesn't delete resource record sets before the time to live (TTL) on the registrar's name servers expires. Route 53 DNS services don't respond to DNS queries for a domain name until the TTL period for the domain name server records elapses. For more information, see I changed DNS settings, but they haven't taken effect.
Linux commands for looking up the registrar or name servers
whois <domain-name> | grep -i registrar
whois <domain-name> | grep -i "name server"
Check for DNS MX record set issues
- To confirm that an MX record for the domain exists, run the following commands:
Linux or macOS
dig DOMAIN_NAME MX
This returns an output similar to the following dig example:
$ dig amazon.com MX
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.2 <<>> amazon.com MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61726
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;amazon.com. IN MX
;; ANSWER SECTION:
amazon.com. 300 IN MX 5 amazon-smtp.amazon.com.
;; Query time: 1 msec
;; SERVER: 10.10.0.2#53(10.10.0.2)
;; WHEN: Wed Apr 14 06:21:43 UTC 2021
;; MSG SIZE rcvd: 67
Windows
nslookup -type=MX DOMAIN_NAME
This returns an output similar to the following nslookup example:
$ nslookup -type=MX amazon.comServer: 10.10.0.2
Address: 10.10.0.2#53
Non-authoritative answer:
amazon.com mail exchanger = 5 amazon-smtp.amazon.com.
- To confirm that you can resolve the MX record hostname, run the following commands:
Linux or macOS
dig MX_RECORD
This returns an output similar to the following dig example:
$ dig amazon-smtp.amazon.com
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.2 <<>> amazon-smtp.amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64180
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;amazon-smtp.amazon.com. IN A
;; ANSWER SECTION:
amazon-smtp.amazon.com. 27 IN A 52.94.124.7
;; Query time: 1 msec
;; SERVER: 10.10.0.2#53(10.10.0.2)
;; WHEN: Wed Apr 14 06:41:18 UTC 2021
;; MSG SIZE rcvd: 67
Windows
nslookup MX_RECORD
This returns an output similar to the following nslookup example:
$ nslookup amazon-smtp.amazon.comServer: 10.10.0.2
Address: 10.10.0.2#53
Non-authoritative answer:
Name: amazon-smtp.amazon.com
Address: 52.119.213.154
Note: Some DNS providers require that you prepend an at symbol (@) to an MX record set name. Or, providers might require you to create an MX record set with the name "@" when creating an MX record set for a root domain. However, don't prepend Route 53 MX record set names with the "@" or any other symbol. To create an MX record set for a root domain in Route 53, leave the record set name blank. Then, provide appropriate values for the remaining fields of the Route 53 MX record set.
For an overview of how DNS works, please refer to the following documentation: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic.
For more information on how to make Route 53 the DNS service for a domain that’s in use, please see, https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html.
For more information on adding or changing name servers and glue records, please refer to the following documentation: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html.
Relevant content
- asked 4 years ago
- asked a year ago
- asked 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago