☰

OSX Lion 上的 DNS

tag-icon • tag-icon domain-name-system mac-osx mac-osx-server dns-hosting
OSX Lion 上的 DNS

我运行的是 OSX Server (10.6)，它运行着一个支持多个域 (A 记录、MX) 的 DNS 服务器。一切都很顺利，直到两天前，我停止接收电子邮件。

我没有对服务器配置做任何更改。我只是不知道这是为什么。我粘贴了 DNS 日志，希望这能有所帮助。

我刚刚重启了服务器，但什么都没变。请提问，我会尽我所知尽力回答。

谢谢！

08-Feb-2013 13:03:59.331 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.203.230.10#53
08-Feb-2013 13:03:59.333 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.58.128.30#53
08-Feb-2013 13:03:59.335 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 193.0.14.129#53
08-Feb-2013 13:03:59.337 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.5.5.241#53
08-Feb-2013 13:03:59.340 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.112.36.4#53
08-Feb-2013 13:03:59.342 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 198.41.0.4#53
08-Feb-2013 13:03:59.347 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 202.12.27.33#53
08-Feb-2013 13:03:59.349 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 199.7.83.42#53
08-Feb-2013 13:03:59.351 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.228.79.201#53
08-Feb-2013 13:03:59.353 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.33.4.12#53
08-Feb-2013 13:03:59.355 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 199.7.91.13#53
08-Feb-2013 13:03:59.357 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 192.36.148.17#53
08-Feb-2013 13:03:59.359 lame server resolving 'B.ROOT-SERVERS.NET' (in 'ROOT-SERVERS.NET'?): 128.63.2.53#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:503:c27::2:30#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:503:ba3e::2:30#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:dc3::35#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:3::42#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2d::d#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:7fe::53#53
08-Feb-2013 13:03:59.360 host unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::803f:235#53
08-Feb-2013 13:03:59.397 success resolving 'B.ROOT-SERVERS.NET/AAAA' (in 'ROOT-SERVERS.NET'?) after reducing the advertised EDNS UDP packet size to 512 octets
08-Feb-2013 13:04:02.927 host unreachable resolving 'local/SOA/IN': 2001:7fe::53#53
08-Feb-2013 13:04:02.927 host unreachable resolving 'local/SOA/IN': 2001:500:2f::f#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:500:1::803f:235#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:dc3::35#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:503:c27::2:30#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:7fd::1#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:503:ba3e::2:30#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:500:3::42#53
08-Feb-2013 13:04:02.928 host unreachable resolving 'local/SOA/IN': 2001:500:2d::d#53
08-Feb-2013 13:05:03.329 host unreachable resolving 'local/SOA/IN': 2001:7fe::53#53
08-Feb-2013 13:05:03.329 host unreachable resolving 'local/SOA/IN': 2001:500:2f::f#53
08-Feb-2013 13:05:03.329 host unreachable resolving 'local/SOA/IN': 2001:500:1::803f:235#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:500:3::42#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:500:2d::d#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:7fd::1#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:503:c27::2:30#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:dc3::35#53
08-Feb-2013 13:05:03.330 host unreachable resolving 'local/SOA/IN': 2001:503:ba3e::2:30#53

答案1

查看您的防火墙设置。

UDP 端口 53 是否有可能不是是否允许进入系统？网络基础设施最近是否发生过任何变化？

答案2

如果您除了自己运行的服务器之外，还有多个用于域的从属服务器，那么可能会发生您描述的情况，那么您所犯的任何错误都可能只会在事发几天或几周后才会显现出来。

StackExchange 网络最近发生了这种情况：他们将主服务器重新定位到新的 IP 地址，但忘记更新各种区域和从属配置。结果如何？一周内一切正常（根据记录expire中的字段SOA），好像什么事都没发生过一样，但有一天突然一切都停止了。

http://stackstatus.net/post/41085475226/outage-jan-21th-2013
https://meta.stackexchange.com/questions/164444/dns-server-failure-for-all-stack-exchange-sites

您包含的日志似乎与您遇到的问题无关，但以下可能是潜在问题的列表（请注意，根据配置，您在整整 4 周前所做的更改（或者，取决于您的SOA设置TTL，甚至可能是几年！）可能仍然与您仅在 2 天前开始遇到的问题有关）：

  • 防火墙阻止的端口
  • 路由器设置已改变
  • IP 地址已更改
  • 主人几周前就去世了，奴隶们的区域两天前才到期
  • 注册处的一些变化

针对域进行故障排除的最佳方法是从远程位置serverfault.com运行类似的操作，并且也可能会有所帮助，以及。dig @ordns.he.net +trace serverfault.comdig +nssearch serverfault.comdig +multiline SOA serverfault.com

网上还有许多网站可以为您进行各种 DNS 检查，以帮助您识别许多潜在问题。

相关内容