Recently, we had reports that we could not internally resolve a certain .com domain name (discovered by undeliverable e-mails). A lookup using an external server (Google's in our case) resolves the .com name just fine.
Long ago, we had another DNS issue that lead us into implementing the following registry change:
https://support.microsoft.com/kb/968372?wa=wsignin1.0
1. Start Registry Editor (Regedit.exe).
2. Locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
3. On the Edit menu, click New, click DWORD (32-bit) Value , and then add the following value:
Value: MaxCacheTtl
Data Type: DWORD
Data value: 0x2A300 (172800 in decimal = 2 days)
That is the only DNS change that we have made. We are using root hints, but temporarily added Google DNS as a forwarder so that we are able to resolve this .com address.
As a test, I did remove that registry entry, restarted the DNS service and tested again to no avail.
Any starting points?