Reverse DNS (rDNS), PTR Records & RIPE Domain Objects
Reverse DNS (rDNS) maps an IPv4 address back to a hostname through a PTR record. For RIPE-managed resources, reverse DNS delegation can also involve a domain object in the RIPE Database. Hyper ICT provides rDNS, PTR record and reverse delegation assistance for eligible IPv4 resources.
Reverse DNS support for IPv4 resources, including PTR records and RIPE reverse delegation where applicable.
- PTR record configuration
- RIPE domain object support
- Reverse DNS delegation
- Record and nameserver updates
What Is Reverse DNS?
Standard forward DNS maps a hostname to an IP address. Reverse DNS performs the opposite lookup by mapping an IP address back to a hostname through a PTR record.
PTR Records
A PTR record associates an IPv4 address with a hostname and provides the result returned during a reverse DNS lookup.
Reverse DNS Zones
IPv4 reverse DNS uses the in-addr.arpa namespace. A reverse zone can be delegated to authoritative DNS servers that host the relevant PTR records.
RIPE Domain Objects
For resources managed through the RIPE Database, reverse DNS delegation is represented by a domain object containing the authoritative nameservers for the reverse zone.
What Is a RIPE Domain Object?
In the RIPE Database, a domain object is used to register a reverse DNS delegation. For IPv4, the object represents a reverse zone under in-addr.arpa and identifies the authoritative nameservers responsible for that zone.
Reverse Delegation
The domain object connects the relevant IPv4 reverse zone with the DNS servers that are authoritative for that zone.
Nameserver Configuration
The nserver attributes in the RIPE domain object identify the DNS servers to which the reverse zone is delegated.
PTR Records
PTR records are configured inside the authoritative reverse DNS zone. They are separate from the RIPE domain object that controls the delegation of that zone.
Reverse DNS for Real Infrastructure
rDNS is commonly used across hosting environments, routed networks and infrastructure where IP addresses need consistent and identifiable hostnames.
Hosting & VPS
Assign meaningful PTR records to VPS nodes, dedicated servers and other hosted infrastructure. See IPv4 Leasing for Hosting & VPS for related address-space requirements.
- VPS infrastructure
- Dedicated servers
- Hosting platforms
Network Infrastructure
Maintain clear and consistent reverse DNS across routed IPv4 resources and network infrastructure. Explore IPv4 Network Services for related routing and resource support.
- Routed IPv4 resources
- Reverse zone delegation
- Infrastructure identification
Domain Object Management
Configure or update reverse delegation for eligible RIPE-managed IPv4 resources using the appropriate domain object and authoritative nameservers.
- Domain object configuration
- nserver updates
- Reverse delegation support
How rDNS Management Works
Depending on your deployment, we can help with individual PTR records, reverse DNS delegation or the relevant RIPE domain object.
Send Your Requirements
Provide the IPv4 prefix or addresses, required hostnames and, where reverse delegation is needed, the authoritative DNS nameservers.
We Review the Resource
We verify the request against the relevant IPv4 resource and determine whether PTR configuration, delegation or a RIPE domain object update is required.
Configure rDNS
The required PTR records or reverse delegation settings are configured. For applicable RIPE resources, this may include creating or updating the relevant domain object.
Verify Resolution
Verify that the reverse DNS zone is delegated correctly and that the relevant IPv4 addresses resolve to the intended hostnames.
Need IPv4 Resources with rDNS Support?
Hyper ICT provides IPv4 leasing from /24 and above, with reverse DNS, PTR record and reverse delegation support available for eligible deployments.
Flexible IPv4 Capacity
Start with the IPv4 capacity your infrastructure needs today and expand when additional address space is required.
- IPv4 blocks from /24 and above
- Monthly leasing
- No standard setup fee
- No standard deposit
- 24-48 hour testing for eligible deployments
Network Resource Support
IPv4 leasing can be combined with supporting network resource services when your deployment requires them.
- Reverse DNS and PTR records
- RIPE domain object support
- LOA support
- RPKI / ROA services
- RIPE Maintainer services
- BGP assistance
Services Related to Reverse DNS
Reverse DNS is often configured alongside other IPv4 routing, authorization and resource-management requirements.
RIPE Maintainer
RIPE Database object management and Maintainer configuration for eligible resources where applicable.
Letter of Authorization
LOA documentation for eligible IPv4 and BGP deployments.
BGP Assistance
Get help with IPv4 prefix announcements and routing requirements.
Reverse DNS Questions
Common questions about reverse DNS, PTR records, reverse delegation and RIPE domain objects.
What is reverse DNS?
Reverse DNS, or rDNS, maps an IP address back to a hostname. It is the reverse of standard DNS resolution, which maps a hostname to an IP address.
What is a PTR record?
A PTR record is the DNS record used to map an IP address to a hostname during a reverse DNS lookup. PTR records are stored in the authoritative reverse DNS zone.
What is a domain object in the RIPE Database?
A RIPE Database domain object is used to register reverse DNS delegation. For IPv4 resources, it represents a reverse zone under in-addr.arpa and contains the authoritative nameservers used for that delegation.
Is a RIPE domain object the same as a PTR record?
No. The RIPE domain object defines the reverse DNS delegation and authoritative nameservers for a reverse zone. PTR records are individual DNS records inside that zone that map IP addresses to hostnames.
Can you configure rDNS for my leased IPv4 addresses?
Yes, for eligible IPv4 resources leased through Hyper ICT. Depending on the deployment, we can assist with PTR records, reverse delegation or the relevant RIPE domain object.
Can PTR records be updated later?
Yes. If your infrastructure or hostname requirements change, PTR records can be updated for supported IPv4 resources.
Should the PTR hostname resolve back to the same IPv4 address?
Where a service expects forward-confirmed reverse DNS, the hostname returned by the PTR record should also resolve forward to the corresponding IPv4 address. The exact requirement depends on the service using the address.
Do I need rDNS for every IPv4 address?
Not necessarily. Reverse DNS requirements depend on how each IPv4 address is being used and whether the service running on it requires reverse DNS.
Can reverse DNS be delegated to my own DNS servers?
Depending on the IPv4 resource and deployment arrangement, reverse DNS can be delegated to customer-controlled authoritative DNS servers where applicable. For RIPE-managed resources, this can involve configuring the appropriate domain object with the required nameservers.
Need Help with rDNS, PTR Records or RIPE Domain Objects?
Tell us which IPv4 resources you are working with and whether you need PTR records, reverse delegation or RIPE domain object configuration.