[BUG] Windows: api.crc.testing (and everything else) resolves to unknown IP

[jds2001]

General information

• OS: Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Yes

CRC version

version: 1.0.0-beta.3-4.1.11+e97bf65

CRC status

Herein lies the problem - it attempts to connect to some (random) IP in order to get the status. See the exact error below.

ERRO Error occurred: Unable to connect to the server: dial tcp 92.242.140.21:6443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
 - exit status 1

CRC config

PS C:\Users\jonst\Downloads\crc-windows-amd64\crc-windows-1.0.0-beta.3-amd64> .\crc config view
- bundle                             : C:\Users\jonst\.crc\crc_hyperv_4.1.11.crcbundle
- cpus                               : 4
- memory                             : 8192
- nameserver                         :
- pull-secret-file                   :
- vm-driver                          : hyperv
- warn-check-bundle-cached           : true

Host Operating System

PS C:\Users\jonst\Downloads\crc-windows-amd64\crc-windows-1.0.0-beta.3-amd64> systeminfo

Host Name:                 DESKTOP-58J0E1A
OS Name:                   Microsoft Windows 10 Pro for Workstations
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          jonstanley@gmail.com
Registered Organization:   N/A
Product ID:                00391-70000-00000-AA538
Original Install Date:     8/22/2019, 5:32:19 PM
System Boot Time:          9/1/2019, 10:04:51 PM
System Manufacturer:       Dell Inc.
System Model:              Precision 5820 Tower
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~3312 Mhz
BIOS Version:              Dell Inc. 1.11.1, 4/24/2019
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume3
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory:     65,211 MB
Available Physical Memory: 30,910 MB
Virtual Memory: Max Size:  74,939 MB
Virtual Memory: Available: 33,591 MB
Virtual Memory: In Use:    41,348 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-58J0E1A
Hotfix(s):                 8 Hotfix(s) Installed.
                           [01]: KB4506990
                           [02]: KB4462930
                           [03]: KB4465065
                           [04]: KB4470788
                           [05]: KB4486153
                           [06]: KB4503308
                           [07]: KB4512937
                           [08]: KB4511553
Network Card(s):           5 NIC(s) Installed.
                           [01]: Intel(R) Ethernet 10G 2P X550-t Adapter
                                 Connection Name: Ethernet
                                 Status:          Media disconnected
                           [02]: Intel(R) Ethernet Connection (5) I219-LM
                                 Connection Name: Ethernet 2
                                 DHCP Enabled:    Yes
                                 DHCP Server:     N/A
                                 IP address(es)
                           [03]: Intel(R) Ethernet 10G 2P X550-t Adapter
                                 Connection Name: Ethernet 3
                                 Status:          Media disconnected
                           [04]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.248.113
                                 [02]: fe80::c1cb:5866:b3ed:93d1
                           [05]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (external vswitch)
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.188
                                 [02]: fe80::9d45:cc89:5ca6:2ce9
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

1. Start CRC
2. VM successfully created, according to logs IP address discovered
3. However, installation does not complete, due to incorrect IP address used to talk to

Expected

Actual

PS C:\Users\jonst\Downloads\crc-windows-amd64\crc-windows-1.0.0-beta.3-amd64> .\crc start
INFO Checking if oc binary is cached
INFO Checking if CRC bundle is cached in '$HOME/.crc'
INFO Check Windows 10 release
INFO Hyper-V installed and operational
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
INFO Loading bundle: crc_hyperv_4.1.11.crcbundle ...
INFO Creating VM ...
INFO Verifying validity of the cluster certificates ...
INFO Check internal and public dns query ...
INFO Copying kubeconfig file to instance dir ...
INFO Adding user's pull secret and cluster ID ...
INFO Starting OpenShift cluster ... [waiting 3m]
INFO To access the cluster using 'oc', run 'eval $(crc oc-env) && oc login -u kubeadmin -p 78UVa-zNj5W-YB62Z-ggxGZ https://api.crc.testing:6443'
INFO Access the OpenShift web-console here: https://console-openshift-console.apps-crc.testing
INFO Login to the console with user: kubeadmin, password: 78UVa-zNj5W-YB62Z-ggxGZ
ERRO Error occurred: Error approving the node csr Not able to get csr names (exit status 1 : Unable to connect to the server: dial tcp 92.242.140.21:6443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)

From the CRC VM (which has the correct IP address of itself)

[root@crc-56mmj-master-0 ~]# host api.crc.testing
api.crc.testing has address 192.168.248.122

From the Windows host:

PS C:\Users\jonst\Downloads\crc-windows-amd64\crc-windows-1.0.0-beta.3-amd64> nslookup api.crc.testing
Server:  Fios_Quantum_Gateway.fios-router.home
Address:  192.168.1.1

Non-authoritative answer:
Name:    api.crc.testing
Address:  92.242.140.21

I'm not sure how my router would be aware of what that should internally resolve to (that being said, from another location on the Internet api.crc.testing is unresolvable as would be expected. so it's possible there's some funny business going on with my router/FIOS)

Note that the IP address returned means nothing to me - it's not my internal nor external IP, and the reverse DNS of it is unhelpful.

It should be noted that the CRC VM is unable to resolve external names, but is able to resolve internal names. This appears to be the result of bogus nameserver configuration on the CRC VM, but I'm not sure how to proceed.

[root@crc-56mmj-master-0 ~]# cat /etc/resolv.conf
# Generated by CRC
search crc.testing
nameserver 10.88.0.8
nameserver 192.168.248.113

192.168.248.113 is the address of the Windows host on the default vswitch. If I switch the nameserver to the CRC VM in nslookup on the Windows host, I'm able to correctly resolve api.crc.testing, but nothing else.

I'm pretty sure this is just a case of "you're holding it wrong" but I'm not sure how to hold it right 😁

[gbraad]

can you share the result of Get-DNSClientServerAddress "vEthernet (Default Switch)" ?

[jds2001]

No such cmdlet as Get-DNSClientAddress but I'm pretty sure this is what you want.

PS C:\Users\jonst\Downloads\crc-windows-amd64\crc-windows-1.0.0-beta.3-amd64> Get-DNSClientServerAddress -InterfaceAlias "vEthernet (Default Switch)"

InterfaceAlias               Interface Address ServerAddresses
                             Index     Family
--------------               --------- ------- ---------------
vEthernet (Default Switch)          11 IPv4    {192.168.248.122}
vEthernet (Default Switch)          11 IPv6    {}

[jds2001]

FYI, I fixed this. Upon further investigation of the IP returned, it IS meaningful, and a piece of garbage. It's returned by the Verizon DNS servers when they encounter an NXDOMAIN. It's designed to be helpful and point you to a search engine (no doubt both increasing revenue for Verizon and creating difficult to debug issues for users). Pointing my router to alternative DNS servers that actually behave correctly and rebooting my machine fixed the problem. I now have working CRC! Yay!

[gbraad]

It's returned by the Verizon DNS servers when they encounter an NXDOMAIN

ouch. Glad to hear it is working now.

[spsingh1982]

@jds2001
Can you share the exact steps how you fixed this. I am also using Verizon laptop and facing exact same issue.

[jds2001]

@jds2001
Can you share the exact steps how you fixed this. I am also using Verizon laptop and facing exact same issue.

Sure - I'm using the FIOS Quantum Gateway, so I'll provide instructions for that. Login to the device, in the top nav menu go to "My Network". Click the Edit link next to "Broadband Connection (Ethernet/Coax)" and click "Settings". A little way down the page there's an option to configure DNS servers, say "Use the following DNS servers". I used 1.1.1.1 and 8.8.8.8 (two free Internet DNS servers that behave properly) and called it a day. Took me awhile to find this, though!