Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DNS native host resolving no longer works with vz VMs since v1.0.0 #2939

Open
dhealio opened this issue Nov 22, 2024 · 0 comments
Open

DNS native host resolving no longer works with vz VMs since v1.0.0 #2939

dhealio opened this issue Nov 22, 2024 · 0 comments
Labels
bug Something isn't working component/dns component/vz

Comments

@dhealio
Copy link

dhealio commented Nov 22, 2024 •
edited
Loading

Description

When using the vz VM and not using user-v2 networking, the DNS behavior mentioned in the documentation is no longer working as advertised when hostResolver.enabled is true (or unassigned).

This prevents being able to use the native OS resolver, which is needed for VPN configurations, split-DNS setups, as well as mDNS, local /etc/hosts etc.

The breaking change seems to be here, which prevents args.UDPDNSLocalPort etc. from getting assigned.
@dhealio dhealio changed the title DNS hostResolver no longer works with vz VMs since v1.0.0 DNS native host resolving no longer works with vz VMs since v1.0.0 Nov 22, 2024
@nirs nirs added bug Something isn't working component/vz component/dns labels Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working component/dns component/vz
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nirs @dhealio