crc: [BUG] Windows : CRC negatively impacts DNS resolution when not running.

General information

• OS: Windows
• Hypervisor:Hyper-V
• Did you run crc setup before starting it YES

CRC version

crc version: 1.3.0+918756b
OpenShift version: 4.2.10 (embedded in binary)

CRC status

CRC VM:          Stopped
OpenShift:       Stopped
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     24.92GB
Cache Directory: C:\Users\Ozzy\.crc\cache

CRC config

- cpus                                  : 6
- memory                                : 32768

Host Operating System

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362
OS Manufacturer:           Microsoft Corporation

Steps to reproduce

1. Install crc… do the whole crc setup, crc start, use crc for a bit, then do crc stop.
2. Try using a web browser, or building with maven, notice all dns resolutions are now taking multiple seconds to resolve instead of being instant.
3. do crc start (in my case … crc start -n 8.8.8.8)
4. Try using a web browser, or building with maven, notice all dns resolutions are now working as expected again…

Expected

When CRC isn’t running, it shouldn’t be screwing up the platforms dns resolution.

Actual

CRC’s adding of a DNS Server to the default virtual switch means every DNS lookup tries to go to the CRC ip (192.168.75.246 in my case) … which is only available when CRC is running. This lookup adds noticeable seconds to DNS resolutions, and seems to cause issues with Maven/Docker builds that expect DNS lookups to occur in a timely manner.

Removing the DNS entry via the network connections panel with start/run/ncpa.cpl and right clicking vEthernet (Default Switch), double click Internet Protocol Version TCP/IP v4, and removing the ip address from the ‘Use the following DNS server addresses’ box, restored normal DNS behavior to my system.