Question

我有一个路由53区域和一些记录集。我的A地址都没有通过互联网传播，已超过5个小时。我不确定发生了什么事，有人可以帮忙吗？

我的问题与此类似 New domain is both registered with and hosted at AWS Route 53 but resolution fails虽然我的域名注册商是我更新了NS值的另一家提供商。因此，当我转到https://mxtoolbox.com/并解析具有CName的记录集时，它会得到很好的解决，但是任何具有A类型的记录都无法解析。

Answer 1

注意：网站名称被审查 - 在私人聊天期间通过SO披露。我会让@Ruskin决定是否要粘贴网站供人们进一步调查。

https://dnschecker.org/#A/XXX.XXX.com表明它几乎遍布全球。在全球范围内，根NS的DNS更改通常需要24-48小时才能覆盖所有人。

来自华盛顿州西雅图：

dig +add +trace XXX.XXX.com                     

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +add +trace XXX.XXX.com
;; global options: +cmd
.           5   IN  NS  i.root-servers.net.
.           5   IN  NS  d.root-servers.net.
.           5   IN  NS  b.root-servers.net.
.           5   IN  NS  g.root-servers.net.
.           5   IN  NS  h.root-servers.net.
.           5   IN  NS  e.root-servers.net.
.           5   IN  NS  a.root-servers.net.
.           5   IN  NS  m.root-servers.net.
.           5   IN  NS  l.root-servers.net.
.           5   IN  NS  c.root-servers.net.
.           5   IN  NS  f.root-servers.net.
.           5   IN  NS  k.root-servers.net.
.           5   IN  NS  j.root-servers.net.
.           5   IN  RRSIG   NS 8 0 518400 20170504050000 20170421040000 14796 . <snip>
;; Received 525 bytes from 127.0.1.1#53(127.0.1.1) in 2 ms

com.            172800  IN  NS  a.gtld-servers.net.
com.            172800  IN  NS  b.gtld-servers.net.
com.            172800  IN  NS  c.gtld-servers.net.
com.            172800  IN  NS  d.gtld-servers.net.
com.            172800  IN  NS  e.gtld-servers.net.
com.            172800  IN  NS  f.gtld-servers.net.
com.            172800  IN  NS  g.gtld-servers.net.
com.            172800  IN  NS  h.gtld-servers.net.
com.            172800  IN  NS  i.gtld-servers.net.
com.            172800  IN  NS  j.gtld-servers.net.
com.            172800  IN  NS  k.gtld-servers.net.
com.            172800  IN  NS  l.gtld-servers.net.
com.            172800  IN  NS  m.gtld-servers.net.
com.            86400   IN  DS  30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.            86400   IN  RRSIG   DS 8 1 86400 20170506170000 20170423160000 14796 . <snip>
;; Received 866 bytes from 198.97.190.53#53(h.root-servers.net) in 84 ms

XXX.com.        172800  IN  NS  ns-689.awsdns-22.net.
XXX.com.        172800  IN  NS  ns-436.awsdns-54.com.
XXX.com.        172800  IN  NS  ns-1707.awsdns-21.co.uk.
XXX.com.        172800  IN  NS  ns-1169.awsdns-18.org.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20170427044835 20170420033835 27302 com. c/BSwOzn216Af6oPN7R6d2XpLCjeshDHpH/5NiUlCZmqqys0J/JZWzif 7BxbsKUgxML/47n8wwQUOE/ah4QnANvT6UasinS+1PponrcLQXjQI2s5 z4JmrXLieCYUQUuAiO/wf3ZFhdMV2/p3V4pYGF0mH0zQ8M0EcvmAWu7z 66w=
EABGLTFA42VFSQFT6MQ54U3GMAQ2OO4H.com. 86400 IN NSEC3 1 1 0 - EABJP3CV31DMGS2MHVSFR6R5BGG3SG0N NS DS RRSIG
EABGLTFA42VFSQFT6MQ54U3GMAQ2OO4H.com. 86400 IN RRSIG NSEC3 8 2 86400 20170429042916 20170422031916 27302 com. <snip>
;; Received 697 bytes from 192.52.178.30#53(k.gtld-servers.net) in 152 ms

XXX.XXX.com.        300 IN  A   <snip>
XXX.com.        86400   IN  NS  ns-1169.awsdns-18.org.
XXX.com.        86400   IN  NS  ns-1707.awsdns-21.co.uk.
XXX.com.        86400   IN  NS  ns-436.awsdns-54.com.
XXX.com.        86400   IN  NS  ns-689.awsdns-22.net.
;; Received 196 bytes from 205.251.198.171#53(ns-1707.awsdns-21.co.uk) in 19 ms

一台没有它的DNS服务器是澳大利亚墨尔本（太平洋电脑网）：

dig +add +trace XXX.XXX.com @secdns.pacific.net.au

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +add +trace XXX.XXX.com @secdns.pacific.net.au
;; global options: +cmd
;; Received 28 bytes from 61.8.0.101#53(secdns.pacific.net.au) in 172 ms

长话短说：等一天又重新检查，很可能一切都会好起来。

路由53，由于DNS未传播，因此无法访问任何A地址

1 个答案: