Skip to content

When ingress-dns is used with IPv6, the ping from host OS (Windows) fails #14872

@oldium

Description

@oldium

What Happened?

Tested on Windows 11. I followed steps to enable ingress-dns and forward test domain queries to minikube DNS from https://minikube.sigs.k8s.io/docs/handbook/addons/ingress-dns/

Then I tried to ping the configured host, but the ping failed:

#> ping frontend.test
Ping request could not find host frontend.test. Please check the name and try again.

nslookup succeeded, though:

> nslookup frontend.test 172.27.2.177
Server:  UnKnown
Address:  172.27.2.177

Non-authoritative answer:
Name:    frontend.test
Addresses:  172.27.2.177
          172.27.2.177

I checked this with Wireshark and the problem is that my Windows run on IPv6 primarily, so they queried the AAAA query first, but received A response. This is actually invalid and reason why DNS resolution failed.

Kindly please @sharifelgamal to comment/merge Pull Request sharifelgamal/minikube-ingress-dns#4 and update the image version to fix this issue.

Attach the log file

log.txt

Operating System

Windows

Driver

Hyper-V

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions