domain-name-system – 是否可以跟踪DNS查找的委派路径？

概述我正在尝试确定为什么 Nagios主机检查失败(主机名和IP已被更改以保护有罪)： : jmglov@laurana; host www.foo.com;; connection timed out; no servers could be reached: jmglov@laurana; for ns in `grep -o '\([0-9]\+[.]\)\{3\}[0-9]\+$' /e 我正在尝试确定为什么 Nagios主机检查失败(主机名和IP已被更改以保护有罪)：

: jmglov@laurana; host www.foo.com;; connection timed out; no servers Could be reached: jmglov@laurana; for ns in `grep -o '\([0-9]\+[.]\)\{3\}[0-9]\+$' /etc/resolv.conf`; do Ping -qc 1 $ns; donePing 192.168.1.1 (192.168.1.1) 56(84) bytes of data.--- 192.168.1.1 Ping statistics ---1 packets transmitted,1 received,0% packet loss,time 0msrtt min/avg/max/mdev = 10.911/10.911/10.911/0.000 msPing 192.168.1.2 (192.168.1.2) 56(84) bytes of data.--- 192.168.1.2 Ping statistics ---1 packets transmitted,time 0msrtt min/avg/max/mdev = 0.241/0.241/0.241/0.000 ms

所以我知道我的名字服务器是可以访问的,这意味着我的主机的权威名称服务器的委托路径中的某个名称服务器没有响应.有没有一种简单的方法来确定这是哪个名称服务器(基本上是DNS的traceroute)？

解决方法 这对你有用吗？

dig +trace Google.com

从手册页：

+[no]trace Toggle tracing of the delegation path from the root name servers for the name being looked up. Tracing is Disabled by default. When tracing is enabled,dig makes iterative querIEs to resolve the name being looked up. It will follow referrals from the root servers,showing the answer from each server that was used to resolve the lookup.

总结

以上是内存溢出为你收集整理的domain-name-system – 是否可以跟踪DNS查找的委派路径？全部内容，希望文章能够帮你解决domain-name-system – 是否可以跟踪DNS查找的委派路径？所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。