Ooh. I am a very specialist use case here, but if you were interested to develop this a little, I have a related use case I would like to solve!
I kind of want the reverse. I have (very) expensive bandwidth and want to block AAAA queries because I know that none of my links will support ipv6 in the near future, with the exception of VPNs and internal lan networks. So I kind of want to run AAAA queries for known specific domains and then every other query will go to the default upstream, where I want some complicated and as yet known process to block those queries and return some sensible answer (Current thinking is to use IPTables to block unwanted AAAA on expensive links and then to avoid problems with resolvers, to have dnsmasq turn the BLOCKED response into a NODATA or similar). Nasty, but not got better ideas So I would be interested in a way to positively accept specific AAAA, but tag all others as undesirable Cheers Ed W On 21/03/2023 11:48, Petr Menšík wrote: > I would prefer to use --filter-AAAA and expand it to accept also /domain/ > modifier, just like > --address or --server. Reusing --address seems confusing, especially with > negated !AAAA syntax. I > think --address serves already too many different purposes. I would not add a > new one if we have > already better option present. Similar way with --filter-A. I think it would > be easier to document > and more intuitive at the same time. > > Does this code handle differences between NXDOMAIN and empty NOERROR answers? > It seems to me it > does not. It would make every name under /domain/ existing but empty. Do we > want that this way? It > may confuse some caching software. > > Cheers, > Petr _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
