lima-vm / lima-vm/lima

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

Open
#2,939 18 comments 6 reactions 0 assignees View on GitHub
bug component/dns component/vz regression
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

### Description

When using the `vz` VM and not using user-v2 networking, the DNS behavior mentioned in the [documentation](https://lima-vm.io/docs/config/network/#dns-19216853) 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](https://github.com/lima-vm/lima/pull/1626/files#diff-6a911aa7574099e18369e9477b214a031077350dedc30e60b933ad0f61e022c2R259), which prevents `args.UDPDNSLocalPort` etc. from getting assigned.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.