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
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
> we are using PowerDNS version 4.2.2 and seeing errors creating subdomains via
> the api.
>
> The following curl worked for years [1], but after an update to latest pdns
> version it is returning 500 http errors:
>
> curl -i -s -XPATCH \
> -H 'X-API-Key: $powerdns_api_key' \
> https://$power
Hi Aki,
>> we are using PowerDNS version 4.2.2 and seeing errors creating subdomains
>> via the api.
>>
>> The following curl worked for years [1], but after an update to latest pdns
>> version it is returning 500 http errors:
>>
>> curl -i -s -XPATCH \
>> -H 'X-API-Key: $powerdns_api_key' \
>
Hi list,
we are using PowerDNS version 4.2.2 and seeing errors creating subdomains via
the api.
The following curl worked for years [1], but after an update to latest pdns
version it is returning 500 http errors:
curl -i -s -XPATCH \
-H 'X-API-Key: $powerdns_api_key' \
https://$powerdns_ho
