dnsmasq not binding to penguin container's external IP

[cbeley]

A helpful reader found what may be a new issue with my write-up at https://chrisbeley.com/software-engineering/how-to-apply-chromeos's-linux-container's-etchosts-outside-of-the-container-in-chrome . This would also require some changes to beleyenv to fix.

TODO:

• Investigate what changed/verify the fix.
• Update beleyenv
• Update the blog post and include a changelog at the bottom noting this change.

Issue sent:

I encountered some problems with this on the latest ChromeOS that you might be interested in. Presumably things have changed with crostini since you wrote that article,
I experienced the below issue on Buster and Bullseye (Version 100.0.4896.82 (Official Build) (64-bit))

The problem was essentially that the ip address returned by "dig +short penguin.lxd" is not the IP address which dnsmasq binds on by default.

The extra step required to make things work after installing dnsmasq is:

1. edit /etc/dnsmasq.conf as root
2. uncomment #listen_address and set it to the IP returned by "dig +short penguin.lxd"
3. sudo systemctl restart dnsmasq