Search for:

Available article translations:

Domain name resolution does not work properly inside a Windows Virtual Machine/Container

Article ID: 119079, created on Dec 9, 2013, last review on Aug 12, 2014

  • Parallels Operations Automation 5.5
  • Parallels Cloud Server 6.0
  • Parallels Virtuozzo Containers for Windows
  • Parallels Server


Domain name resolution inside a Windows container/virtual machine does not work correctly:

  • Nslookup query is successful:

    Non-authoritative answer:
    Addresses:  2a00:1450:4002:800::1001
  • pinging IP address is successful;
  • pinging FQDN returns could not find host error message:

    Ping request could not find host Please check the name and try again.


Such behavior can be caused by misconfiguration of domain search parameters of Windows TCP/IP stack


In case only one virtual machine/container is affected:

  1. RDP into the virtual machine/container (for containers and virtual machines with Parallels Tools installed you can use vzctl enter CTID and prlctl enter VMNAME commands from the node)

  2. Execute the following command:

    C:\>reg add "HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters" /v Domain /t reg_sz

    (Instead of using Command Prompt you can open Registry Editor and add an empty Domain String value to the "HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters" key)

  3. Reboot the virtual machine/container

In case the problem affects all newly created containers:

Reinstall the OS template using instructions from this article:

In case the issue affects all virtual machines created from a particular template:

  1. Create a virtual machine from the affected template:

    # prlctl create TempVM --type vm --ostemplate WindowsTemplateName
  2. Start this virtual machine:

    # prlctl start TempVM
  3. RDP to the virtual machine

  4. Create C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup\prl_set_domain.cmd file with the following content:

    @echo off
    reg query "HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters" /v Domain >NUL 2>&1
    if x%ERRORLEVEL%x NEQ x0x (reg add "HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters" /v Domain /t reg_sz)
  5. Add it to startup scripts

  6. Stop the temporary virtual machine, and clone it to template:

    # prlctl stop TempVM
    # prlctl clone TempVM --name WindowsTemplateName2 --template

Additional information

The issue has been fixed completely since Parallels Cloud Server 6.0.5 Update 5 Hotfix 2 (6.0.5-1784)

All PCS updates can be installed via:

    #yum update

NOTE: Once updates are installed it is necesary to update Parallels Tools inside of affected Windows template.

Search words:


PACI: Проблема с DNS

909d99074e442b52ce54cc7b31cf065d 2897d76d56d2010f4e3a28f864d69223 4542fc1e09dcc36ad9dbfd547b6b7b3c f61d9c3a6d233f5fda89aa20fffd1398 caea8340e2d186a540518d08602aa065 64cafed7cc15bceb3b240d8c2f92dce3 c65eaff5333f2b87eda32041b8ac987f 3d9560cc94370f9e1bd9256d230e5ee8 bf1c3a170005eae151f49ba2720abde9 ca05eaf5b843fbd53589c90d7228a6df bb8d08f557ff7e4b314b6bbaa846b034

Was this article helpful?
Tell us how we may improve it.
Yes No
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0
- Parallels Virtuozzo Containers
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification