On 20/10/2022 14:17, qutic development via Pdns-users wrote:
Thank you Brian for taking note! That was my bad in the email cause I changed
the real ipv6-address into a sample one.
https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/
___
Hi Thomas,
thank you for taking a look into it!
My fault was the dot at the end of "ip6.arpa", without it it is now working
well!
- Stefan
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-u
>> In the domains-table there is a record with name
>> "0.0.0.0.0.8.b.d.1.0.0.2.ip6.arpa."
>
> That's wrong. It should be 0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
>
> - that is, the original address is really 2001:0db8::/48 (when you write out
> all 4 hex digits, and don't omit the leading zero)
Thank
On 20/10/2022 12:55, qutic development via Pdns-users wrote:
In the domains-table there is a record with name
"0.0.0.0.0.8.b.d.1.0.0.2.ip6.arpa."
That's wrong. It should be 0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
- that is, the original address is really 2001:0db8::/48 (when you write
out all 4 hex
Hi,
surely this was answered before, but I did not found any answers to my question.
We do have PowerDNS with a gmysql backend. The goal is to get ipv6 PTR working.
Lets asume we do have a 2001:db8::/48.
In the domains-table there is a record with name
"0.0.0.0.0.8.b.d.1.0.0.2.ip6.arpa." for t
Hello,
This is the release of version 4.7.0 of the Authoritative Server.
4.7.0 brings support for [1]Catalog Zones, developed by Kees
Monshouwer. As part of that development, the freshness checks in the
Primary code were reworked, reducing them from doing potentially
thousands of SQL queries (if
