问题原文
原帖链接 · Gareth Boden · CC BY-SA 3.0
My network admins have created a DNS record for thedigitalteacher.com which should include an A record for the domain root pointing to 5.10.124.142, which is indeed the response I get if I use our internal name servers.
However, Google's name servers on 8.8.8.8 frequently (but not always) fail to resolve the name, leading to this kind of nonsense:
ahrcsdca01115:triangle-app bodeng$ nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> thedigitalteacher.com
Server: 8.8.8.8
Address: 8.8.8.8#53
** server can't find thedigitalteacher.com: NXDOMAIN
> set querytype=any
> thedigitalteacher.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: thedigitalteacher.com
Address: 5.10.124.142
thedigitalteacher.com nameserver = ns0.dcdns.net.
thedigitalteacher.com nameserver = ns1.dcdns.net.
thedigitalteacher.com nameserver = ns2.dcdns.net.
thedigitalteacher.com nameserver = ns3.dcdns.net.
thedigitalteacher.com
origin = ns0.dcdns.net
mail addr = domains.ucles.org.uk
serial = 22
refresh = 900
retry = 600
expire = 86400
minimum = 3600
thedigitalteacher.com mail exchanger = 10 66.96.140.160.
Authoritative answers can be found from:
> set querytype=a
> thedigitalteacher.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: thedigitalteacher.com
Address: 5.10.124.142
How can I figure out what's wrong with this domain?
社区高分解答
原帖链接 · Håkan Lindqvist · CC BY-SA 3.0
It would seem that you are using some nameserver internally that works reliably, while the nameservers used by everyone else is in a worse state.
The delegation looks like this:
;; AUTHORITY SECTION:
thedigitalteacher.com. 172800 IN NS ns0.dcdns.net.
thedigitalteacher.com. 172800 IN NS ns1.dcdns.net.
thedigitalteacher.com. 172800 IN NS ns2.dcdns.net.
thedigitalteacher.com. 172800 IN NS ns3.dcdns.net.
;; ADDITIONAL SECTION:
ns0.dcdns.net. 172800 IN A 192.149.119.100
ns1.dcdns.net. 172800 IN A 192.149.119.100
ns2.dcdns.net. 172800 IN A 192.149.119.100
ns3.dcdns.net. 172800 IN A 212.44.18.27
There are four NS records but, as you can see, these effectively boil down to only two addresses, 192.149.119.100 and 212.44.18.27.
212.44.18.27 seems to consistently answer with a referral to the root (indicating it simply doesn't know about thedigitalteacher.com), while 192.149.119.100 produces a mix of actual answers and referrals to the root.
As for what causes the 192.149.119.100 behavior, I can only speculate. Maybe 192.149.119.100 is backed by multiple server instances which are out of sync?
It looks to be a bit of a mess on the authoritative end.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
