-
Notifications
You must be signed in to change notification settings - Fork 236
-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CheckCRCLocalDNSReachableFromHost should check the IP it resolves #1013
Comments
cfergeau
added a commit
to cfergeau/crc
that referenced
this issue
Feb 26, 2020
…mHost CheckCRCLocalDNSReachableFromHost checks that the api.crc.testing and foo.apps-crc.testing hostnames can be resolved, but it does not check this returns the IP of the VM. This commit adds an additional check that the resolved IP matches the IP of the VM as this could help crc detect some host misconfigurations early. This resolves crc-org#1013
cfergeau
added a commit
to cfergeau/crc
that referenced
this issue
Feb 27, 2020
…mHost CheckCRCLocalDNSReachableFromHost checks that the api.crc.testing and foo.apps-crc.testing hostnames can be resolved, but it does not check this returns the IP of the VM. This commit adds an additional check that the resolved IP matches the IP of the VM as this could help crc detect some host misconfigurations early. This resolves crc-org#1013
cfergeau
added a commit
to cfergeau/crc
that referenced
this issue
Feb 27, 2020
cfergeau
added a commit
to cfergeau/crc
that referenced
this issue
Feb 28, 2020
…mHost CheckCRCLocalDNSReachableFromHost checks that the api.crc.testing and foo.apps-crc.testing hostnames can be resolved, but it does not check this returns the IP of the VM. This commit adds an additional check that the resolved IP matches the IP of the VM as this could help crc detect some host misconfigurations early. This resolves crc-org#1013
praveenkumar
pushed a commit
that referenced
this issue
Mar 2, 2020
CheckCRCLocalDNSReachableFromHost checks that the api.crc.testing and foo.apps-crc.testing hostnames can be resolved, but it does not check this returns the IP of the VM. This commit adds an additional check that the resolved IP matches the IP of the VM as this could help crc detect some host misconfigurations early. This resolves #1013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently CheckCRCLocalDNSReachableFromHost tries to resolve api.crc.testing and foo.crc-apps.testing, but it's not verifying they resolved to the VM IP
It's possible to have non-working DNS configurations where unknown names would resolve to an IP, so it would be better to check we resolved these hostnames to a known IP.
The text was updated successfully, but these errors were encountered: