Dnsmasq No Longer Working After Upgrade To v0.14.2 [Brew] about warden HOT 6 CLOSED

@bap14 @navarr Thanks for coming back to me on this. The stuff you sent over definitely pointed me in the right direction. I checked the /etc/resolver/test file on my local system and it contained the following;

nameserver 127.0.0.1
port 5053

I updated this to;

nameserver 127.0.0.1

And everything is now working as expected. Big thank you for everyones help!

from warden.

@ryan-copeland logs looks good to me

I remember having similar issue with browser VPN enabled, but then I had ERR_TUNNEL_CONNECTION_FAILED error so it doesn't look like your case.

from warden.

Hi @ryan-copeland
Have you tried running warden svc down && warden svc up after upgrade?
If the issue still persists you can check dnsmasq logs under Orbstack context menu -> warden -> dnsmasq -> Logs

from warden.

Hi @arendarenko - Thanks for replying on this ticket. I ran the following commands after the upgrade;

warden svc down -v && warden svc up

But this has still resulted in any .test domain not being pointed at 127.0.0.1. The logs from dnsmasq can be seen below;

[webproc] 2024/05/24 06:56:08 loaded config file '/etc/dnsmasq.conf' from disk
[webproc] 2024/05/24 06:56:08 agent listening on http://0.0.0.0:8080...
dnsmasq: started, version 2.90 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-cryptohash no-DNSSEC loop-detect inotify dumpfile
dnsmasq: using nameserver 1.0.0.1#53
dnsmasq: using nameserver 1.1.1.1#53
dnsmasq: read /etc/hosts - 9 names

That all seems to look ok from what I can see. Is there some sort of configuration in warden that needs to be changed to enable dnsmasq?

from warden.

@ryan-copeland Just to be sure, did you add the .test domain to your system's resolver so it knows to look to DNSMasq to resolve anything ending in .test? https://docs.warden.dev/configuration/dns-resolver.html

from warden.

Additionally, the latest information regarding dnsmasq not working correctly is here: #262 (comment)

Sadly whenever this issue crops up it is very environment-specific

from warden.