Reverse DNS on cloudflare

dash-dns
#1

I have 3 free domains registered in cloudflare. Recently i’ve purchased a /24 subnet and i want to set reverse DNS for it.
I’ve created PTR records in cloudflare DNS interface and i wanted to create a domain-object in RIPE interface for my subnet to point to the nameservers cloudflare assigned to me but when i do this, i get the error “Nameserver dean.ns.cloudflare.com/173.245.59.153 did not return NS records. RCODE was REFUSED.”

Am i doing something wrong?

This is the full error message:

SUMMARY OF UPDATE:

Number of objects found:                   1
Number of objects processed successfully:  0
  Create:         0
  Modify:         0
  Delete:         0
  No Operation:   0
Number of objects processed with errors:   1
  Create:         1
  Modify:         0
  Delete:         0

DETAILED EXPLANATION:

***Warning: Invalid keyword(s) found: 1s
***Warning: All keywords were ignored

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following object(s) were found to have ERRORS:

- ---
Create FAILED: [domain] 220.131.185.in-addr.arpa

domain:         220.131.185.in-addr.arpa
descr:          WIRD-SOLUTIONS-SRL
descr:          WIRD SOLUTIONS SRL
descr:          Mihai Bravu, nr. 204 Bl. 105, sc. 2, ap. 44
descr:          Bucuresti Sect. 3
admin-c:        WSN11-RIPE
tech-c:         WSN11-RIPE
zone-c:         WSN11-RIPE
nserver:        dean.ns.cloudflare.com
nserver:        nia.ns.cloudflare.com
mnt-by:         RO-MNT
changed:        [email protected] 20190308
source:         RIPE

***Error:   Nameserver dean.ns.cloudflare.com/173.245.59.153 did not return NS
            records. RCODE was REFUSED.

***Error:   Nameserver dean.ns.cloudflare.com/2400:cb00:2049:1::adf5:3b99 did
            not return NS records. RCODE was REFUSED.

***Error:   Nameserver nia.ns.cloudflare.com/173.245.58.210 did not return NS
            records. RCODE was REFUSED.

***Error:   Nameserver nia.ns.cloudflare.com/2400:cb00:2049:1::adf5:3ad2 did not
            return NS records. RCODE was REFUSED.

***Error:   Not enough data about 220.131.185.in-addr.arpa was found to be able
            to run tests.
#3

anyone???

#4

If it was possible, it would only be available to Enterprise customers and even then would need to be discussed with your account manager.

#5

I believe the OP is not referring to a Cloudflare address space but to his own 185.131.220.0/24 and I understand he would like to delegate 220.131.185.in-addr.arpa to Cloudflare’s nameservers. Unfortunately my knowledge about PTRs is way too spotty to dare to make any statement in this regard. @mnordhoff maybe.

1 Like
#6

My general understanding of PTR records is they need to be set by the people who sold you the block of addresses.

#7

Yes, that’s exactly what i need to do.

#8

The people who sold my the block of addresses create a delegation for this block to some NS servers. And on that NS servers you create PTR records.
The problem is, when they created the delegation to cloudflare’s NS servers, they received that error.

#9

It didn’t work because you have a zone called example.com or whatever, not 220.131.185.in-addr.arpa.

Unless you’re on an enterprise plan, Cloudflare unfortunately won’t run an in-addr.arpa zone for you.

1 Like
closed #10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.