Hi Sven, Yes, I tried adding ::1 localhost to hosts.dnsmasq, and it enables the dig command to succeed. I also tried adding host records pointing to ::1 for each current record that points to 127.0.0.1 in this file.
For the purposes of this discussion I need to assume that this isn't a complete solution since the problem space extends beyond getting the dig command to exit with code zero, since our tests fail during the configuration phase with these changes applied. As far certain components of our system outside of my immediate purview are concerned, there's a difference between "NODATA-IPv6 / NOERROR / NXDOMAIN" with "ANSWER: 0", versus "AAAA record found" with "ANSWER: 1", versus "AAAA record not found, REFUSED". Cheers, -Casey On Sat, Aug 31, 2024 at 10:24 AM Sven Geuer <s...@debian.org> wrote: > > Hi Casey, > > On Fri, 2024-08-30 at 13:42 -0700, Casey Tucker via Dnsmasq-discuss > wrote: > > I don't know whether the way it worked before was intended or an > > emergent property of previously undefined behavior, but since we need > > it to do as it did before, we now need to patch and compile dnsmasq > > with a revert commit instead of directly consuming upstream Ubuntu > > Did you try to alter the hosts.dnsmasq file like this? > > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > > Note the repeated 'localhost' with ::1. > > Cheers, > Sven > > -- > GPG Fingerprint > 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
