Hey Evandro,
chaching of arbitrary types has been added this year in March and is
available in the latest master code (option --cache-rr). You can even
add --cache-rr=ANY to cache all records.
See
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=638c7c4d20004c0f320820098e29df62a27dd2a1
Hey Evandro,
see my reply to your other question as the questions are just two
aspects of the same thing:
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2023q4/017363.html
Best,
Dominik
P.S. Your address evandro+dnsm...@gcc.gnu.org throws an "user unknown"
error.
On Thu,
Before I went and hacked it, I figured that it’d be better to float the idea,
in case it’d been discussed before and deemed not worthy the while.
--
Evandro Menezes
> Em 7 de dez. de 2023, à(s) 14:37, Geert Stappers
> escreveu:
>
> On Thu, Dec 07, 2023 at 01:03:16PM -0600, Evandro Menezes
} Subject: Caching of NS and SOA records
On Thu, Dec 07, 2023 at 01:03:16PM -0600, Evandro Menezes wrote:
> These records are not cached, right? In my anecdotal experience, they
> represent just 2 to 5% of the queries. Though these records are not
> very common, their TTL is fairly high, so it
Current OSes are now using the HTTPS record to query the addresses and the
canonical name, as well other information important to browsers, rather than
using the A and records as they used to.
In my anecdotal experience, HTTPS queries amount to over a third of the
queries. It might make
These records are not cached, right? In my anecdotal experience, they
represent just 2 to 5% of the queries. Though these records are not very
common, their TTL is fairly high, so it might make sense to cache them as well,
since their replies necessarily gate subsequent queries, which would
