Hello!
On 8/30/21 2:13 PM, labs--- via Pdns-users wrote:
I tried the 1.6.0.38 version but the problem still exists. I can see
that you backported the patch 29 days ago but the 1.6.0.38 package is
dated 18th may 2021. Does this version really contain the patch? Perhaps
there should be newer nig
Hello Remi,
Am 27.08.21 um 17:47 schrieb Remi Gacogne via Pdns-users:
Note that the fix has already been backported to the rel/dnsdist-1.6.x
branch and we automatically build packages from that branch so in the
meantime you could use these. Look for 1.6.0.* directories under [1],
like [2]. T
Hi
Has anyone got an example of PTR records in .yaml backend
Thanks
Tony
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
Thank you both; I do now at least understand why it's behaving as it is; I
missed that the first response was actually from the com server, and therefore
authoritative for adpclaims.com.
Obviously I support Frank's feature request, but unfortunately I'm not able to
offer much in the way of "how
Hi,
I think I have to clarify a bit here. The first question was why the
recursor doesn't accept the A records from the delegated name server’s
response. For the record I believe we are talking about this response,
received from one of the servers returned in the delegation from one of
the co
Hi Paul,
This is a design choice by PowerDNS, which is defendable: the domain is
misconfigured and the RFCs don't clearly which option to take in such a case.
Unfortunately, Google and Unbound toke a different option, so when the customer
verifies against 8.8.8.8, it will just work. Also unfort