On 1/23/19 2:08 PM, Thomas Mieslinger wrote:
> Lets take the output of
>
> dig +dnssec ns-de.ui-dns.de @a.nic.de
>
> as an example. If the additional section was tweaked, pdns_recursor has
> no real chance to detect this.
That's actually a very good example because unless I'm mistaken, ever
Hello Peter,
thanks to confirm
In the configuration file there are few *cache-ttl
So I wasn't completely sure
It works as expected and the testing tool on dnsfladay.net gives green light
Thanks
De'
From: Pdns-users On Behalf Of
Peter van Dijk
Sent: 22 January 2019 13:56
To: pdns-users@mailma
We use PowerDNS "Graphing as a service",
https://blog.powerdns.com/2014/12/11/powerdns-graphing-as-a-service/
for our pdns-recursor installations. Environment:
FreeBSD 11.2, PowerDNS Recursor 4.1.8, carbon-server=37.252.122.50.
This works well, with one minor but slightly irritating exception:
Hi Remi,
On 1/23/19 10:04 AM, Remi Gacogne wrote:
[..] >> In short I would like that pdns_recursor does not use information from
additional sections. Just like pdns authoritative 4.1.x does not
generate additional sections anymore.
Completely ignoring additional records would break zones that
Hi Thomas,
On 1/23/19 8:01 AM, Thomas Mieslinger wrote:
> I would like to better understand how pdns_recursor 4.1.x deals with
> records in the additional section of replies it gets from authoritative
> Servers.
These records, if the recursor considers that the authoritative server
is allowed to
