我今天在错误日志中发现了这个错误。 我联系了Rackspace Fanatical Support，他们告诉我他们不支持这种事情。 问题是：他们设置了，我不知道服务器configuration。
Event Type: Information Event Source: DnsApi Event Category: None Event ID: 11156 Date: 18/12/2009 Time: 04:06:06 User: N/A Computer: NEWDB Description: The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : {7FB36A51-B9B5-4C8E-B8FE-224466B2F9CB} Host Name : newDB Adapter-specific Domain Suffix : wadja.local DNS server list : 192.168.1.142, 83.138.151.80 Sent update to server : 255.255.255.255 IP Address : 192.168.1.139 The reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. For specific error code information, see the record data displayed below. 任何想法这意味着什么，以及如何解决？
另一个错误：
The processing of Group Policy failed. Windows attempted to read the file \\wadja.local\sysvol\wadja.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled.
在192.168.1.139的服务器和192.168.1.142的DNS服务器之间是否有networking连接问题或防火墙？ DNS是否在.142上运行？ 该错误表示请求更新其networking适配器的资源logging超时。 如果你认为networking是好的，DNS是好的，你可以在客户端和DNS服务器上捕获一个wiresharknetworking跟踪，并查看stream量（你应该能够缩小你的search范围到端口53的stream量），看看是否有任何东西跳向你。 您也可以尝试从客户端上的命令行键入ipconfig / registerdns手动重试DNS注册（如消息所示）。
第二个错误也表明潜在的networking问题…你可以手动到达\ wadja.local \ sysvol \ wadja.local？ 如果是这样，您可以从客户端手动打开\ wadja.local \ sysvol \ wadja.local \ Policies {31B2F340-016D-11D2-945F-00C04FB984F9} \ gpt.ini吗？ 如果不是…再次，networking跟踪可能有助于显示正在发生的事情。
如果您正在运行WIndows Server 2008（并根据您的标记，您是），您也可以尝试运行dcdiag（说明在这里： http ：//technet.microsoft.com/en-us/library/cc731968( WS.10 ）.aspx ）和Active Directory域服务的最佳实践分析器，以查看是否有任何工具标记某些内容。
至于DNS错误，对我来说似乎很正常。 您的服务器configuration为使用公共DNS服务器（83.138.151.80），它试图在反向查找区域（1.168.192.in-addr.arpa）中注册一个RFC1918 PTR地址，该地址不会存在于公共DNS服务器。
至于networking相关的错误，这里是我的build议：
将DNS设置为AD集成DNS。
如果这是唯一的AD \ DNS服务器，则将其configuration为仅使用自身的DNS。
如果您有另一个AD \ DNS服务器，那么每个服务器都使用它自己作为主DNS，而另一个AD \ DNS服务器作为备用DNS。
进行更改后重新启动任何AD \ DNS服务器（只是为了刷新），看看是否错误返回。