You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am really enjoying lima but I have hit a limitation with regards to dns. I have installed lima from brew and it reports as stable 0.21.0 (bottled), HEAD.
I have a VPN connection on my mac that is configured with split DNS. scutil --dns shows me something like:
Lima now provides a DNS server that resolves names on the host, so generally this should work automatically without any configuration.
Which sounds to me like, in the default configuration, a guest's DNS requests should be looked up by the host just like any other program would so the host's split DNS configuration should affect the guest. But at least in my testing this does not seem to be the case. Maybe I am not understanding or the behaviour of lima is different now.
I created an instance with fedora like so. It installed f39:
Inside fedora there is a single nameserver 192.168.5.2:
$ lima resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eth0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.5.2
DNS Servers: 192.168.5.2
DNS Domain: example.com
Inside fedora when anything tries to reach a *.example.com domain it does not get looked up via host resolver #2; everything seems to go to host resolver #1. I can dig @10.20.30.40 test.example.com in the guest and lookups are done as expected, so I am sure I could configure split DNS inside the guest and have it work but it is a bit cumbersome to have to do that for every new instance. And it would be in place regardless of whether the host VPN is active, etc.
Is this just a limitation of what can be done with lima or is there some way to get this to work "out of the box" without having to modify the guest configuration?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am really enjoying lima but I have hit a limitation with regards to dns. I have installed lima from brew and it reports as
stable 0.21.0 (bottled), HEAD
.I have a VPN connection on my mac that is configured with split DNS.
scutil --dns
shows me something like:I read in #270 (comment) someone said:
Which sounds to me like, in the default configuration, a guest's DNS requests should be looked up by the host just like any other program would so the host's split DNS configuration should affect the guest. But at least in my testing this does not seem to be the case. Maybe I am not understanding or the behaviour of lima is different now.
I created an instance with fedora like so. It installed f39:
Inside fedora there is a single nameserver 192.168.5.2:
Inside fedora when anything tries to reach a
*.example.com
domain it does not get looked up via hostresolver #2
; everything seems to go to hostresolver #1
. I candig @10.20.30.40 test.example.com
in the guest and lookups are done as expected, so I am sure I could configure split DNS inside the guest and have it work but it is a bit cumbersome to have to do that for every new instance. And it would be in place regardless of whether the host VPN is active, etc.Is this just a limitation of what can be done with lima or is there some way to get this to work "out of the box" without having to modify the guest configuration?
Beta Was this translation helpful? Give feedback.
All reactions