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

[dhealio]

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]

To be more specific, DNS resolving of VPN hostnames on macOS was working on v0.23.2 when starting lima with the default configuration/parameters, but no longer works with v1.0.0 or v1.0.1.

FWIW, I have also tried starting lima with user-v2 networking via limactl start --network=lima:user-v2, but I am still unable to resolve VPN hostnames within lima. This seems to contradict the behavior mentioned here, but perhaps I am doing something wrong.

If this is by design, then how would I go about configuring lima to allow DNS resolving of VPN hostnames? The documentation should be updated to reflect any changes of behavior in this regard.

Otherwise, this is a breaking change that I'm hoping can be addressed soon.

[nirs]

Based on the comment this a regression.