跳至内容
使用AWS re:Post即您表示您同意 AWS re:Post 使用条款
AWS re:Postre:Post
关于 re:Post

Route53 Hosted Domain Not working

0

I discovered that my domain that is registered with AWS had different name servers than the hosted name servers. I update the AWS Domain Registrar with the hosted zone name servers. Now, after an hour or so dig is sending me the following error: kevinibt:~ dig NS augusta-mail.com

; <<>> DiG 9.10.6 <<>> NS augusta-mail.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9397 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ; OPT=15: 00 17 5b 32 30 35 2e 32 35 31 2e 31 39 39 2e 34 32 5d 20 72 63 6f 64 65 3d 52 45 46 55 53 45 44 20 66 6f 72 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 2f 6e 73 ("..[205.251.199.42] rcode=REFUSED for augusta-mail.com/ns") ; OPT=15: 00 17 5b 32 30 35 2e 32 35 31 2e 31 39 32 2e 32 30 36 5d 20 72 63 6f 64 65 3d 52 45 46 55 53 45 44 20 66 6f 72 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 2f 6e 73 ("..[205.251.192.206] rcode=REFUSED for augusta-mail.com/ns") ; OPT=15: 00 17 5b 32 30 35 2e 32 35 31 2e 31 39 36 2e 37 35 5d 20 72 63 6f 64 65 3d 52 45 46 55 53 45 44 20 66 6f 72 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 2f 6e 73 ("..[205.251.196.75] rcode=REFUSED for augusta-mail.com/ns") ; OPT=15: 00 17 5b 32 30 35 2e 32 35 31 2e 31 39 34 2e 36 32 5d 20 72 63 6f 64 65 3d 52 45 46 55 53 45 44 20 66 6f 72 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 2f 6e 73 ("..[205.251.194.62] rcode=REFUSED for augusta-mail.com/ns") ; OPT=15: 00 16 41 74 20 64 65 6c 65 67 61 74 69 6f 6e 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 20 66 6f 72 20 61 75 67 75 73 74 61 2d 6d 61 69 6c 2e 63 6f 6d 2f 6e 73 ("..At delegation augusta-mail.com for augusta-mail.com/ns") ;; QUESTION SECTION: ;augusta-mail.com. IN NS

;; Query time: 132 msec ;; SERVER: 192.168.40.1#53(192.168.40.1) ;; WHEN: Sun Sep 28 21:41:08 EDT 2025 ;; MSG SIZE rcvd: 346

Any idea as to why this is occuring?

主题
网络和内容交付
标签
亚马逊 53 号线路
语言
English
已提问 1 个月前34 查看次数
2 回答
0

The SERVFAIL error you're seeing indicates there's still an issue with your domain's nameserver configuration. This typically happens when there's a mismatch between the nameservers listed at the registrar level and those in your Route 53 hosted zone.

Here are the likely causes and solutions:

  1. Propagation Delay: DNS changes can take up to 24-48 hours to fully propagate globally. Since you only made the changes an hour ago, you may need to wait longer for the changes to take effect.

  2. Nameserver Mismatch: Double-check that the nameservers in your domain registration settings exactly match those in your Route 53 hosted zone. You can verify this by:

  • Opening your Public Zone in Route 53 and noting the 4 NS Records
  • Going to the Registered Domains section in Route 53 and confirming they match

  1. Multiple Hosted Zones: If you have more than one hosted zone with the same name (augusta-mail.com), make sure you're using the nameservers from the correct hosted zone.

  2. Missing or Incorrect Records: Ensure you've created the necessary DNS records in your hosted zone.

To troubleshoot further:

  • Run a whois command to check your registrar-level nameservers and compare them with your hosted zone nameservers
  • Verify that all four AWS nameservers are correctly listed in your domain registration
  • Clear your local DNS cache to ensure you're not seeing cached results

If the issue persists after 24-48 hours, you might need to contact AWS Support through the Account and Billing section, which is available at no additional charge for domain registration issues.
Sources
Route 53 owned domain is not being resolved | AWS re:Post
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
Resolve website access issues in Amazon Route 53 | AWS re:Post
My domain is unavailable on the internet - Amazon Route 53

已回答 1 个月前
专家
已审核 1 个月前
0

When I lookup the name servers for your domain augusta-mail.com.

I see:

% dig -t NS augusta-mail.com.

; <<>> DiG 9.10.6 <<>> -t NS augusta-mail.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23963
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
augusta-mail.com.	86400	IN	NS	ns1.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns2.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns3.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns4.bdm.microsoftonline.com.

;; Query time: 40 msec
;; SERVER: 80.254.79.7#53(80.254.79.7)
;; WHEN: Mon Sep 29 09:07:38 CEST 2025
;; MSG SIZE  rcvd: 137

This seems to be behaving as expected, if this is the delegation set that you have provided in the AWS Console for your registered domain.

AWS
专家
已回答 1 个月前
专家
已审核 1 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈，并能促进提问者的职业发展。

相关内容