On 16/12/13 11:13, Tomas Hozza wrote:
- Original Message -
I can see at least one bug in the code: in the code-path taken to answer
a query from the cache, the value of the AD flag is never changed: it
simply takes the value that it had in the query. I guess the
authenticated status of
- Original Message -
I can see at least one bug in the code: in the code-path taken to answer
a query from the cache, the value of the AD flag is never changed: it
simply takes the value that it had in the query. I guess the
authenticated status of the data should be cached, and used
On 11/12/13 13:52, Tomas Hozza wrote:
Hi.
I have been trying to understand what --proxy-dnssec option does.
From what I understand if NOT used, dnsmasq will NOT forward the
AD flag set by the upstream server to its clients.
If the --proxy-dnssec option is used, dnsmasq WILL forward the
AD
Hi.
I have been trying to understand what --proxy-dnssec option does.
From what I understand if NOT used, dnsmasq will NOT forward the
AD flag set by the upstream server to its clients.
If the --proxy-dnssec option is used, dnsmasq WILL forward the
AD flag in the DNS answer IF it was set by the
