Skip to content

pkg/networks/usernet: use domain.tld zones#4772

Open
julego wants to merge 1 commit intolima-vm:masterfrom
julego:usernet-dns-zones
Open

pkg/networks/usernet: use domain.tld zones#4772
julego wants to merge 1 commit intolima-vm:masterfrom
julego:usernet-dns-zones

Conversation

@julego
Copy link
Copy Markdown

@julego julego commented Mar 24, 2026

The usernet client stores dns records in tld zones, and as such the default host.lima.internal record breaks resolving .internal domains that may exist on the host network (e.g. compute.internal, dev.internal, etc).

This is a proposal to store dns records in domain.tld zones to be able to use such domains.

It may close #3161 also.

Signed-off-by: Julien Le Goff <julego@gmail.com>
@AkihiroSuda
Copy link
Copy Markdown
Member

CI failing

ping: lima-net-user-v2-1.internal: Name or service not known

https://github.com/lima-vm/lima/actions/runs/23485110542/job/69213743913?pr=4772

@AkihiroSuda AkihiroSuda removed this from the v2.1.1 milestone Mar 31, 2026
@julego
Copy link
Copy Markdown
Author

julego commented Apr 7, 2026

I just checked the test, it failed because the dns server implemented in gvisor-tap-vsock doesn't seem to handle domain.tld zones so well.

With domain.tld zones, sublevel records such as project.dev.tld are well resolved by gvisor-tap-vsock (what I was testing on my dev env) but root records like dev.tld are not (whether the tld is ".internal" or not). Hence the test failing with "lima-net-user-v2-1.internal".

I'll have a look at this but gvisor-tap-vsock will probably need a patch too, I don't think there's a direct fix in lima.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Resolving .internal domains from inside the container

2 participants