It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.
If you check your servers event viewer you will see EVENT ID 1056: The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. Credentials for Dynamic DNS registrations may be configured using the command line “netsh dhcp server set dnscredentials” or via the DHCP Administrative tool.
Using the "Diagnose problem" feature in the Manage Network Interfaces panel results in a message claiming that it cannot reach the DNS server and that the connection needs to be reset. It is connected to a DSL router via an ethernet cable.
If you are working with, well almost anything network intensive these days, like Antivirus or management tools, your Reverse DNS (r DNS) lookups need to be in good shape.Declarations about network topology include the declaration is required for each subnet even if no addresses will be dynamically allocated on that subnet.Some installations have physical networks on which more than one IP subnet operates.If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices.