Closed f-w closed 3 years ago
Make sure you are not on VPN when testing this (currently a known issue)
Try to override the nameserver in the VM with -n [nameserver]
on start.
Not on vpn. Set to what nameserver?
Set to what nameserver?
I don't know how your network is configured. Something local (if router caches/forwards), your ISPs, or a public one if possible?
My network uses name server provided by my ISP. The name server resolves to only IPV6 address. I think that's the root cause. Works when I run crc start -n 8.8.8.8
.
If crc only supports IPV4 name server, then it should be documented as a prerequisite.
The name server resolves to only IPV6 address. I think that's the root cause
crc is not IPv4 only, but might experience issues with IPv6 as this is not fully tested.
On Wed, Jul 29, 2020 at 10:01 PM Fred notifications@github.com wrote:
My network uses name server provided by my ISP. The name server resolves to only IPV6 address. I think that's the root cause. Works when I run crc start -n 8.8.8.8. If crc only supports IPV4 name server, then it should be documented as a prerequisite.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop! [ Better Understanding Involves Learning and Doing ]
@praveenkumar this is an interesting one to look at: 'when name server resolves only to IPV6'.
@gbraad Agree, I think in the past also we experienced same issue.
Just to clarify, it's the first name server that is IPv6. I still have IPv4 name servers.
C:\Users\x>nslookup
Default Server: node-1w7jr9n24twqrzrke3a0v8lzn.ipv6.telus.net
Address: 2001:568:ff09:10a::53
>
C:\Users\x>ipconfig /all
...
DNS Servers . . . . . . . . . . . : 2001:568:ff09:10a::53
2001:568:ff09:10a::114
192.168.1.254
75.153.171.114
2001:568:ff09:10a::53
2001:568:ff09:10a::114
...
@gbraad should we add this as known issue.
For now, yes... Until we have a clearer answer.
We need to run more tests with IPv6
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@gbraad Does this issue apply to all platforms? Getting this documented.
Just noticed that this was never closed. We have this documented as a known issue in the release notes downstream. :)
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
After
crc start
andcrc console
Expected
No error
Actual
Got following reproducible errors
Same operations work on OpenShift Online.
Note
crc start
doesn't give any error on DNS queryOther information