Reverse DNS Delegation for IPv4 Networks
IPv4 reverse DNS maps an address to a hostname through pointer (PTR) records under in-addr.arpa. Prepare authoritative DNS and arrange delegation with the administrator of the parent reverse zone. Control of a forward domain or a BGP announcement alone does not grant that authority.
Before changing reverse DNS
Have the exact prefix, the intended hostnames, access to authoritative DNS and a contact who can change the parent delegation. For third-party address space, agree whether you receive DNS delegation or only a provider-managed PTR editing service. Record this alongside the address-space responsibility checklist.
The examples below use documentation addresses and reserved example names. They describe a configuration to adapt, not working public DNS. Replace the addresses, names and zone boundaries before running the queries against your network.
| Item | Example or responsibility |
|---|---|
| Address | 192.0.2.129 |
| Reverse lookup name | 129.2.0.192.in-addr.arpa. |
| Usual /24 reverse zone | 2.0.192.in-addr.arpa. |
| PTR target | mail.example.net. |
| Parent administrator | Publishes delegation and any classless mappings |
| Child DNS operator | Serves the agreed zone and maintains PTR records |
| Forward-domain operator | Maintains the target hostname’s A/AAAA records |
Confirm the actual zone cut with the parent administrator. A larger prefix can involve several zones; a small subnet does not automatically become a direct DNS delegation at its CIDR boundary. The CIDR reference helps identify the addresses involved.
In this conceptual classless example, the parent supplies a CNAME and child delegation, the child supplies the PTR, and the returned hostname is checked in a separate forward lookup. The hostname’s DNS zone and the reverse zone can have different administrators. Arrows show record relationships and checks, not packet routing.
View full diagramIdentify the reverse zone and its administrator
For 192.0.2.129, reverse the octets and append in-addr.arpa. A useful starting observation is:
dig +trace -x 192.0.2.129Follow the referrals to identify the last delegated zone and its name servers. A failed trace can also reflect local network restrictions, so compare with the parent operator’s view before concluding that no delegation exists. Registry records help find the responsible resource contact; the actual DNS answers establish the current delegation.
Write down who can change parent NS records, who hosts the child zone, and who will handle changes when the address arrangement ends. A tenant should not assume it has registry-maintainer access.
Prepare authoritative DNS before requesting delegation
For a complete /24, an illustrative zone fragment is:
$ORIGIN 2.0.192.in-addr.arpa.
$TTL 3600
@ IN SOA ns1.example.net. hostmaster.example.net. (
2026111901 3600 900 1209600 3600 )
IN NS ns1.example.net.
IN NS ns2.example.net.
129 IN PTR mail.example.net.The trailing dots make the server names and PTR target absolute. Name server (NS) records identify the zone’s servers. The start of authority (SOA) record identifies its primary server and contact; the serial is a version counter to increase when publishing changes. Use values appropriate to your DNS service rather than copying the example serial repeatedly.
Query each intended authoritative server directly, before moving the delegation:
dig @ns1.example.net 2.0.192.in-addr.arpa SOA +norecurse
dig @ns2.example.net 2.0.192.in-addr.arpa NS +norecurse
dig @ns1.example.net 129.2.0.192.in-addr.arpa PTR +norecurse
dig @ns1.example.net 2.0.192.in-addr.arpa SOA +norecurse +tcpExpect authoritative answers, the intended NS set, consistent zone content and the correct PTR. Test both servers over UDP and TCP port 53. A server that resolves ordinary names recursively may still fail to serve this zone authoritatively.
Arrange the parent delegation or classless mapping
Send the exact reverse zone, name servers, change owner and test results to the parent administrator. For RIPE-managed reverse delegations, the RIPE reverse DNS procedure describes the authorized domain object and pre-delegation checks, including at least two authoritative servers. A provider may manage a lower-level parent instead; use the mechanism that controls your actual zone cut.
For 192.0.2.128/25, a classless arrangement can use the following agreed example child name. It is not a naming rule every provider must use:
; Parent: 2.0.192.in-addr.arpa.
128-255 IN NS ns1.example.net.
128-255 IN NS ns2.example.net.
129 IN CNAME 129.128-255.2.0.192.in-addr.arpa.
; Child zone: 128-255.2.0.192.in-addr.arpa.
; Add its own SOA and NS records, then the PTR:
129 IN PTR mail.example.net.The parent needs the agreed CNAME mappings for the relevant addresses; the single line above demonstrates only address .129. The child operator cannot create those mappings by adding them solely to the child zone. This pattern is described in the classless reverse-delegation specification.
If reverse DNS is signed, coordinate the child keys and parent DS records with both administrators. An old DS referring to a replaced key can make validating lookups fail even when a direct unsigned-style query returns data. Keep signing changes in the handover plan rather than removing security records as a general workaround.
Verify the public lookup and forward confirmation
After the parent change, repeat the trace and query the child servers. Then query a recursive resolver outside your authoritative DNS service:
dig +trace -x 192.0.2.129
dig -x 192.0.2.129
dig mail.example.net AFor the classless example, the chain should lead through the expected CNAME target to mail.example.net.. If forward-confirmed reverse DNS is required by a service, the hostname’s forward answer must include 192.0.2.129; a PTR pointing at a name that resolves elsewhere does not pass that comparison.
Record authoritative and recursive results separately. Delegation publication, record TTLs, cached negative answers and resolver refreshes affect when observers agree. A portal success message is not the final DNS test.
Troubleshoot failures and preserve the handover path
| Observation | Next check |
|---|---|
| Child answers correctly; trace reaches old servers | Parent NS delegation and cached referrals |
| Parent points to new servers; they do not answer authoritatively | Zone loaded under the correct name, authoritative service and firewall |
| A small subnet’s child zone answers but public lookup fails | Parent CNAME mapping and delegation for that exact address |
| Direct lookup works; validating resolver returns SERVFAIL | DNSSEC validation, parent DS and child DNSKEY consistency |
| PTR exists but the service rejects it | Forward confirmation and the service’s independent requirements |
| Only some recursive resolvers disagree | TTLs, negative caches and the observed answer’s source |
During a DNS migration, keep the old authoritative service available until the new delegation and records work from the required observation points and cached referrals have been considered. Coordinate stale-record removal with the parent administrator when returning space.
A PTR change does not publish a country or city correction. Use the IP-geolocation correction workflow for that separate task. For a proposed deployment, confirm DNS-control responsibilities when discussing the address delivery arrangement.