没有NSlogging的工作域。 可能?

有没有NSlogging可以有工作的Alogging(工作网站)?

mylinux:~# dig example.com NS ; <<>> DiG 9.3.4-P1.2 <<>> example.com NS ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18501 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;example.com. IN NS ;; AUTHORITY SECTION: example.com. 336 IN SOA NS1.1MORENAME.com. hostmaster.example.com. 5 28800 7200 604800 86400 ;; Query time: 1 msec ;; SERVER: 194.126.115.18#53(194.126.115.18) ;; WHEN: Mon Feb 28 12:17:56 2011 ;; MSG SIZE rcvd: 90 mylinux:~# telnet example.com 80 Trying 50.22.26.210... Connected to example.com. Escape character is '^]'. GET / <tml> <head> <title></title> <meta name="description" content=" information from ekodomains.com. Find the best sites on the web." > <meta name="keywords" content="" > [....] 

尝试dig +trace example.com Adig +trace example.com NS来查看引荐是如何发生的。 .com域名服务器必须有NSlogging作为.com区域的一部分,但它引用的名称服务器可能没有为该区域configurationNSlogging。

通常BIND拒绝加载没有NSlogging的区域,但其他的DNS软件可能更宽容。

在search具有相同名称服务器的其他域之后,他们以这种方式行事似乎并不罕见:

 ; <<>> DiG 9.7.0-P1 <<>> @ns1.1morename.com keyzweb.com ns ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16653 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;keyzweb.com. IN NS ;; AUTHORITY SECTION: keyzweb.com. 86400 IN SOA NS1.1MORENAME.com. hostmaster.keyzweb.com. 1 28800 7200 604800 86400 ;; Query time: 123 msec ;; SERVER: 173.236.119.110#53(173.236.119.110) ;; WHEN: Sat Mar 5 11:06:05 2011 ;; MSG SIZE rcvd: 90 

这是一个跟踪,显示NS​​在委托点logging(在这种情况下,由.com域名服务器返回的NSlogging)不是权威性的。 这就是为什么他们不显示为答案:它们不存在于权威的域名服务器中。

 ; <<>> DiG 9.7.0-P1 <<>> +trace keyzweb.com ns ;; global options: +cmd . 22664 IN NS l.root-servers.net. . 22664 IN NS f.root-servers.net. . 22664 IN NS h.root-servers.net. . 22664 IN NS a.root-servers.net. . 22664 IN NS g.root-servers.net. . 22664 IN NS m.root-servers.net. . 22664 IN NS i.root-servers.net. . 22664 IN NS d.root-servers.net. . 22664 IN NS c.root-servers.net. . 22664 IN NS k.root-servers.net. . 22664 IN NS j.root-servers.net. . 22664 IN NS e.root-servers.net. . 22664 IN NS b.root-servers.net. ;; Received 509 bytes from 10.19.12.20#53(10.19.12.20) in 0 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. ;; Received 492 bytes from 193.0.14.129#53(k.root-servers.net) in 22 ms keyzweb.com. 172800 IN NS ns1.1morename.com. keyzweb.com. 172800 IN NS ns2.1morename.com. ;; Received 107 bytes from 192.26.92.30#53(c.gtld-servers.net) in 102 ms keyzweb.com. 86400 IN SOA NS1.1MORENAME.com. hostmaster.keyzweb.com. 1 28800 7200 604800 86400 ;; Received 90 bytes from 173.236.119.110#53(ns2.1morename.com) in 124 ms 

几件事情:

1)“example.com”是一个保留的域名,根据RFC 2606.它在GTLD区域有特殊的地位,因为这个最佳实践。 它的保留主要是为了让写文档,书籍等的人能够使用/引用一个“示例”域名,而不会使读者感到困惑(或者吸引不必要的stream量)。

2)上面的海报是正确的:example.com有两个名称服务器列在iana-servers.net。 validation这一点的最好方法就是像parsing器那样走树。

– > dig @ f.gtld-servers.net example.com ns – > nslookup -type = example.com。 f.gtld-servers.net。 ('type'可以是任何'any','a'/'aaaa','mx',txt'等) – > host example.com f.gtld-servers.net

从你原来的post,我 – 我很怀疑。 SOA不匹配。 “1morename”不是example.com的正确SOA。 这是你的ISP吗? 如果是这样,我不知道他们是否为了自己的利益而欺骗DNS。 (如果不是,也许,你正在使用的Linux发行版?)

从根TLD根服务器尝试请求NS:

 $ dig com. NS ; <<>> DiG 9.7.0-P1 <<>> com. NS ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18638 ;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;com. IN NS ;; ANSWER SECTION: com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. $ dig example.com NS @c.gtld-servers.net ; <<>> DiG 9.7.0-P1 <<>> example.com NS @c.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28957 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 4 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;example.com. IN NS ;; AUTHORITY SECTION: example.com. 172800 IN NS a.iana-servers.net. example.com. 172800 IN NS b.iana-servers.net. 

然后从TLD根服务器查询Alogging:

 $ dig example.com A @c.gtld-servers.net ; <<>> DiG 9.7.0-P1 <<>> example.com A @c.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18291 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 4 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;example.com. IN A ;; AUTHORITY SECTION: example.com. 172800 IN NS a.iana-servers.net. example.com. 172800 IN NS b.iana-servers.net. ;; ADDITIONAL SECTION: a.iana-servers.net. 172800 IN A 199.43.132.53 a.iana-servers.net. 172800 IN AAAA 2001:500:8c::53 

可以通过,Alogging来自TLD服务器。