Can I host a delegated reverse ip ipv6 submet in cloudflare DNS service?

[soeren.schroeder]

What is the name of the domain?

7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa.

What is the issue you’re encountering

I’m not sure if it is possible to host a delegated zone in cloudflare at all

What steps have you taken to resolve the issue?

NS record for zone has been created. But zone is still “pending”

host -t NS 7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:

7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa name server anton.ns.cloudflare.com.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa name server wally.ns.cloudflare.com.

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

NS records points to cloudflare NS

host -t NS 7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:

7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa name server anton.ns.cloudflare.com.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa name server wally.ns.cloudflare.com.

[michael]

@soeren.schroeder

I’m not sure if it is possible to host a delegated zone in cloudflare at all

It is possible. I host all of my reverse DNS on Cloudflare without issue for many years.

Please share a screenshot of the DNS panel of the Cloudflare dashboard if you are having issues. It looks like you have PTR records pointing back to the original nameservers, perhaps you had a wildcard PTR record previously.

It used to be an Enterprise only feature, but I believe that restriction is now gone. (You will need a paid plan if you have more than 200 records per reverse zone)

Reverse zones and PTR records | Cloudflare DNS docs

These should be DNS only (everything ). You used to get certificates for the reverse zones, which was interesting but not really useful.

[soeren.schroeder]

screenshot of panel as requested

and zone export of same:

7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa 3600 IN SOA anton.ns.cloudflare.com. dns.cloudflare.com. 2048194531 10000 2400 604800 3600

;; NS Records
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 86400 IN NS anton.ns.cloudflare.com.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 86400 IN NS wally.ns.cloudflare.com.

;; PTR Records
1.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.5.7.0.7.c.6.f.5.0.a.2.ip6.arpa.7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1 IN PTR n111.chaos.dk.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1 IN PTR snabela.chaos.dk.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1 IN PTR new-dsl-root.chaos.dk.
7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1 IN PTR dsl-root.chaos.dk.

[michael]

Screenshot says that the zone is active:

@soeren.schroeder

;; PTR Records
1.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.5.7.0.7.c.6.f.5.0.a.2.ip6.arpa.7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa. 1 IN PTR n111.chaos.dk.

That does not look correct. It looks like you tried to add a PTR record for an IP address in a different delegation (1.5.7.0.7.c.6.f.5.0.a.2.ip6.arpa). That is currently pointing at broken nameservers under gratisdns.dk

The other resolves just fine:

% dig +short PTR 7.4.1.8.7.c.6.f.5.0.a.2.ip6.arpa @anton.ns.cloudflare.com.
dsl-root.chaos.dk.
new-dsl-root.chaos.dk.
snabela.chaos.dk.

[soeren.schroeder]

Thanks for the help - I guess the main trick was to wait “up to 24 hours” for the zone to get active. … And to be carefull to no mix up different zones

[epic.network]

You may also want to pick one of the three PTRs that you have for the same IP and delete the other two. While DNS does not prohibit the same IP returning multiple PTR records, it is not recommended.