应该何时终止NS查询?

时间:2015-09-16 08:40:35

标签: dns

命令:

. 1664 IN NS a.root-servers.net. . 1664 IN NS b.root-servers.net. . 1664 IN NS c.root-servers.net. . 1664 IN NS d.root-servers.net. . 1664 IN NS e.root-servers.net. . 1664 IN NS f.root-servers.net. . 1664 IN NS g.root-servers.net. . 1664 IN NS h.root-servers.net. . 1664 IN NS i.root-servers.net. . 1664 IN NS j.root-servers.net. . 1664 IN NS k.root-servers.net. . 1664 IN NS l.root-servers.net. . 1664 IN NS m.root-servers.net. ;; Received 228 bytes from 8.8.4.4#53(8.8.4.4) in 200 ms com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. ;; Received 500 bytes from 192.33.4.12#53(192.33.4.12) in 27 ms google.com. 172800 IN NS ns2.google.com. google.com. 172800 IN NS ns1.google.com. google.com. 172800 IN NS ns3.google.com. google.com. 172800 IN NS ns4.google.com. ;; Received 164 bytes from 192.52.178.30#53(192.52.178.30) in 119 ms google.com. 345600 IN NS ns4.google.com. google.com. 345600 IN NS ns2.google.com. google.com. 345600 IN NS ns1.google.com. google.com. 345600 IN NS ns3.google.com. ;; Received 164 bytes from 216.239.38.10#53(216.239.38.10) in 25 ms

输出:

config/session.js

解析器在收到192.52.178.30(com的名称服务器之一)的答案后没有终止查询。这是标准行为吗?它适用于所有类型的记录吗?

1 个答案:

答案 0 :(得分:0)

您要求dig为您提供权威名称服务器的跟踪,并为您提供了对权威名称服务器的跟踪。我不明白为什么你会感到惊讶。或者,换句话说,是的,当您在+trace中使用dig时,这完全是预期的行为。