DNS name resolution fails for "A" record in Windows Server 2012

In a Windows Server 2012 or Windows Server 2012 R2 environment, you discover that you can't resolve a hostname to an IPv4 address when you use a single label name instead of a fully qualified domain name (FQDN). In this situation, you receive the following error message:

Name does not exist
To work around this issue, use one of the following methods:
  • Use an FQDN instead of a single label name.
  • Disable negative caching. To do this, create and configure the following registry entry:

    Registry : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
    Name of the key : MaxNegativeCacheTtl
    Data Type : REG_DWORD
    Value : 0
DNS, "Name does not exist"

Article ID: 3064504 - Last Review: 07/05/2015 19:34:00 - Revision: 4.0

Windows Server 2012 Standard, Windows Server 2012 Datacenter, Windows Server 2012 Foundation, Windows Server 2012 Essentials, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1, Windows 8.1 Pro, Windows 8.1 Enterprise, Windows 8, Windows 8 Pro, Windows 8 Enterprise

  • kbexpertiseadvanced kbsurveynew kbtshoot KB3064504