Search

Language:  
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

APPLIES TO:
  • Operations Automation 5.5
  • Virtuozzo 6.0
  • Virtuozzo containers for Windows
  • Virtuozzo hypervisor

Symptoms

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

  • Nslookup query is successful:

    C:\>nslookup google.com
    nslookup google.com
    Non-authoritative answer:
    Server:  ns1.bell.net.mt
    Address:  217.168.160.42
    
    Name:    google.com
    Addresses:  2a00:1450:4002:800::1001
              173.194.113.231
              173.194.113.232
    
  • pinging IP address is successful;
  • pinging FQDN returns could not find host error message:

    C:\>ping google.com
    ping google.com
    Ping request could not find host google.com. Please check the name and try again.
    

Cause

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

Resolution

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:

ping

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




d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef a26b38f94253cdfbf1028d72cf3a498b 614fd0b754f34d5efe9627f2057b8642

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