You cannot normally assign a different PTR hostname to every domain sharing one public IP. A PTR record belongs to the IP address, and the organization that owns that address—usually your VPS provider—controls its reverse-DNS zone. With one address, choose one canonical fully qualified domain name (FQDN), point that name to the address with an A or AAAA record, and set the address’s PTR to it. The other domains can still run websites and mail on the same VPS, but they use the same reverse-DNS identity.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
If each domain needs its own reverse identity, give each one a separate public IP, or obtain a delegated reverse-DNS block that you can manage yourself.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhat a PTR record does
A PTR (pointer) record answers the reverse-DNS question: “Which hostname is associated with this IP address?” For IPv4, resolvers query the corresponding name beneath in-addr.arpa; IPv6 uses ip6.arpa. This is the opposite direction from an ordinary A record, which maps a hostname to an IPv4 address, or an AAAA record, which maps a hostname to an IPv6 address.
Reverse zones are normally delegated to the IP address holder. A domain registrar or the authoritative DNS service for example-a.com therefore cannot set the PTR for an unrelated address. The VPS company that assigned the address must expose a reverse-DNS field, accept a support request, or delegate the reverse zone to you.
#1 Best Overall
RFC 1912 recommends a matching PTR for every address assigned to a host, including every address on a multi-homed server. That means the task starts with an inventory of all public IPv4 and IPv6 addresses that can originate traffic, not with a list of hosted domains.
Why a normal DNS zone cannot answer a reverse query
When a resolver looks up 203.0.113.10 in reverse, it asks for the PTR at 10.113.0.203.in-addr.arpa. That name belongs to the address owner’s reverse hierarchy, not to the forward zone for example-a.com. IPv6 performs the same operation under ip6.arpa, using the address’s hexadecimal nibbles in reverse order. Adding a PTR-shaped record to a website’s ordinary DNS zone therefore has no effect on reverse lookups.
Can several domains have separate PTRs on one IP?
In the normal provider-managed model, no. One public address has one effective PTR hostname. For example, if 203.0.113.10 serves example-a.com, example-b.com, and example-c.com, you could select mail.example-a.com as the canonical name, create an A record for it, and set the address’s PTR to that name. The other two domains remain valid virtual hosts, but reverse lookups of 203.0.113.10 return the single canonical hostname.
Entering several PTR values in a provider form does not create dependable round-robin reverse DNS. Provider documentation commonly rejects multiple values, and software that happens to return more than one answer is not a reliable way to give each domain a distinct identity. Hetzner explicitly states that more than one PTR cannot be added per IP address, while Oracle documents a one-to-one connection between a PTR and an IP address.
| Deployment design | PTR identities | Suitable when | Important trade-off |
|---|---|---|---|
| Several domains on one public IP | One canonical hostname | Web hosting, shared applications, or mail that can use one server identity | All outbound connections from that address present the same reverse name |
| One public IP per domain or service | One per address | Customers or services require distinct reverse identities | Additional addresses may cost extra and require provider approval |
| Delegated reverse-DNS block | One per address in the delegated range | You operate a sufficiently large address block and need direct reverse-zone control | You must run and secure the reverse zone correctly |
Plan the names and addresses before changing DNS
Inventory every source address
List each public IPv4 and IPv6 address that the VPS may use for SMTP, web callbacks, APIs, monitoring, or other outbound traffic. Include secondary addresses and addresses configured on additional interfaces. If an application binds to IPv6, treat that address as a separate reverse-DNS task; an IPv4 PTR does not cover it.
Rank #2
- Linux
- Linux DNS
Choose one stable FQDN per address
Use a name that identifies the machine or service and will remain valid if you add another hosted domain. Names such as mail.example-a.com or vps1.example-a.com are common choices. Do not choose a temporary provider hostname if you intend to use a custom identity, and do not attempt to make one address represent every hosted domain.
The name does not have to match every visible website or From address. It should instead be a durable label for the system using that source address. If one hostname intentionally serves both IPv4 and IPv6, publish both corresponding records and make sure both addresses have appropriate PTR entries.
Check provider capability
Before assigning the address to production traffic, confirm that the VPS provider permits custom reverse DNS. The control may be called “rDNS,” “reverse DNS,” or “PTR.” Some providers offer an editable field in the instance or IP page; others require a support ticket. Also confirm that both IPv4 and IPv6 can be customized, whether extra addresses are available, and whether a delegated reverse block is an option.
Step-by-step: configure one canonical PTR
- Record the address. Write down the exact public address, such as
203.0.113.10. For IPv6, preserve the full address, for example2001:db8::10, and verify that it is the address applications actually use. - Publish forward DNS first. In the authoritative zone for the canonical hostname, create an A record such as
mail.example-a.com A 203.0.113.10. For IPv6, createmail.example-a.com AAAA 2001:db8::10. Use the exact address assigned to the VPS, not an internal address or a different NAT endpoint. - Allow the forward record to become visible. Check the authoritative answer before requesting the PTR. A provider may reject a reverse entry when the hostname does not yet resolve, and forward-confirmation prevents an inconsistent configuration.
- Open the provider’s reverse-DNS control. In a self-service panel, select the relevant IP address and enter the complete FQDN, including its domain suffix. Do not enter only
mail, and do not add a trailing space or a URL. - Use support when there is no field. Send the provider the address and the exact FQDN, for example: “Set the PTR for 203.0.113.10 to mail.example-a.com.” For IPv6, include the full address and request its reverse entry separately.
- Wait for the provider’s change window. Reverse-DNS timing, TTL, and any approval process are provider-specific. Keep the provider’s stated propagation interval with your deployment notes instead of assuming an immediate global update.
- Verify the reverse answer. Run
dig -x 203.0.113.10 +short. The expected answer is the canonical hostname, such asmail.example-a.com.. For IPv6, rundig -x 2001:db8::10 +short. - Verify the forward answer. Run
dig mail.example-a.com A +shortand confirm that203.0.113.10appears. For IPv6, rundig mail.example-a.com AAAA +shortand confirm2001:db8::10. Repeat both checks for every address that originates traffic.
The two directions should form a deliberate match: the PTR points to a hostname, and that hostname’s A or AAAA data points back to the same address. A name that resolves elsewhere leaves the reverse identity ambiguous and can trigger policy checks by systems that expect forward-confirmed reverse DNS.
Hosting and sending for the other domains
Virtual hosting does not require a separate PTR for every website. Configure the web server with each domain’s host name and leave the address’s reverse identity set to the canonical FQDN. DNS records for example-b.com and example-c.com can still point to the same address through their own A or AAAA records.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Mail requires a clear operational choice. If several domains send through one address, configure the server’s primary hostname and outbound identity consistently with the canonical PTR. The PTR is an address-level property; changing the visible From domain does not create another reverse record. If a customer or receiving system requires the connection to reverse-resolve to that customer’s own name, use a different source address for that traffic rather than trying to attach multiple PTR values to one address.
A correct PTR is only one part of mail acceptance. Provider rules about outbound SMTP, port 25, abuse handling, and account approval still apply. Check those rules before buying extra addresses or moving a mail service. A provider that blocks the intended traffic cannot be made suitable merely by setting a technically valid reverse record.
Costs and address planning
One shared address keeps the reverse-DNS design simple, but separate identities generally mean ordering or attaching additional public addresses. Providers may charge for those addresses and may require approval, justification, or a particular plan. The exact price and availability vary by provider, region, address family, and product, so treat the provider’s current pricing and policy as the authority.
Delegated reverse space can avoid changing a PTR through a panel for every address, but it is intended for customers controlling a sufficiently large subnet. You must operate authoritative nameservers and maintain the zone, so administration and monitoring become part of the cost. A single VPS address does not normally justify that complexity.
When separate PTR identities are genuinely required
Assign separate public addresses
Request one public IPv4 or IPv6 address for each identity that must be independently reverse-resolvable. Give each address its own hostname, publish matching A or AAAA data, and set one PTR through the provider. Bind the relevant service to its intended source address so that the reverse result matches the traffic leaving the VPS.
Use a delegated reverse zone for a larger block
If you control a sufficiently large subnet, ask the address holder to delegate the reverse zone to your authoritative name servers. RFC 2317 describes the classless IPv4 delegation technique; IPv6 providers use analogous delegation arrangements beneath ip6.arpa. Delegation makes you responsible for serving the zone, maintaining nameservers, and keeping every address’s forward and reverse data accurate. It is not necessary for a single VPS address.
Troubleshooting PTR problems
| Symptom | Likely cause | Fix |
|---|---|---|
dig -x returns the provider’s hostname |
The custom PTR was never submitted, was applied to a different address, or the provider has not completed the change. | Check the exact address in the VPS panel, confirm the requested FQDN, and ask support to verify the reverse-zone entry and its change status. |
You added a PTR inside example-a.com, but reverse lookups ignore it |
The record was placed in a forward zone instead of the address owner’s reverse zone. | Remove the misplaced record and configure reverse DNS through the IP holder. |
| The provider rejects the hostname | The hostname has no visible A or AAAA record, uses an internal address, or is malformed. | Publish the correct forward record first, wait until authoritative DNS answers, then submit the complete FQDN again. |
| Forward and reverse checks disagree | The PTR points to a name whose A or AAAA record points to another address, or the service is sourcing traffic from a secondary address. | Correct the forward record or bind the service to the address whose PTR you intend to use. Re-run both dig commands. |
| Several PTR values appear intermittently | Multiple reverse values were entered or different resolvers have cached old data. | Keep one canonical value for the address, remove unsupported extras through the provider, and allow the documented TTL or change window to pass. |
| IPv4 works but IPv6 does not | Only the IPv4 address was configured, while applications are making connections over IPv6. | Create the IPv6 AAAA record, set the IPv6 PTR separately, and test with dig -x against the IPv6 address. |
| The provider offers no custom reverse DNS | The service policy does not permit customer-managed PTR records. | Ask whether support can set one manually. If not, choose a provider that documents custom rDNS before moving mail or other systems that depend on it. |
How to evaluate a VPS provider for multi-domain reverse DNS
Provider choice determines what you can do after the server is deployed. Compare these capabilities before purchasing an address or migrating a mail service:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Capability to check | Questions to ask | Why it matters |
|---|---|---|
| PTR control method | Is there a self-service field, or must support apply every change? | Self-service speeds corrections; support-mediated changes require a documented process and response time. |
| Protocol coverage | Can you set custom PTRs for both IPv4 and IPv6? | A server that originates IPv6 traffic needs a separately managed reverse identity. |
| Additional addresses | Can you order or attach more public addresses, and under what approval rules? | Separate identities require separate addresses unless you receive a reverse-zone delegation. |
| Forward-confirmation behavior | Does the panel validate A or AAAA data, and what happens when a record is missing? | Validation catches mismatches before they affect production traffic. |
| Delegated reverse space | Can an eligible customer delegate a block and host its own reverse zone? | This is relevant to larger networks, not to ordinary single-address VPS use. |
| Email and abuse policy | Are outbound SMTP, custom rDNS, and port 25 permitted for your plan and region? | A technically correct PTR cannot overcome a provider policy that blocks the intended traffic. |
Operational checklist
- Maintain a written map of every public address, its canonical FQDN, and the service that uses it.
- Keep exactly one intended PTR hostname per address in the provider’s system.
- Publish and test A or AAAA data before requesting reverse DNS.
- Test from the VPS and from an independent resolver with
dig -x, then confirm the forward answer. - Repeat the process for every secondary IPv4 and IPv6 address, not only the first address shown in the control panel.
- Record provider TTLs, approval requirements, and change windows so a future migration does not leave stale reverse names.
- When moving an address between services, update its canonical hostname and forward record together, then verify both directions after the provider applies the change.
What the final configuration should look like
For a shared-IP VPS, the finished arrangement is straightforward: mail.example-a.com has an A record for 203.0.113.10; the reverse lookup of 203.0.113.10 returns mail.example-a.com; and the other hosted domains point to the same address without claiming additional PTR values. If the VPS also uses 2001:db8::10, that address has its own AAAA record and its own PTR, which may use the same canonical hostname only when the hostname intentionally resolves to both addresses.
That one-to-one mapping between an address and its reverse identity is the boundary to design around. Add addresses or obtain reverse-zone delegation when the boundary conflicts with a service requirement; do not try to solve it by adding multiple PTR records to one IP.
Frequently Asked Questions
Can I create one PTR for each domain hosted on my VPS?
Not when the domains share one public IP in the normal provider-managed model. The IP has one effective PTR, so choose one stable canonical hostname. Give each domain its own A or AAAA record for website and application hosting, but they will share the address’s reverse identity.
Best Value
- Standard size: 6 pink server note pads, Each Book Comes with 50 bound order slips - that's 300 ticket sheets total! Check Pads Size 6.75 x 3.5 inch.
- Convenient Work: These guest check books for servers have a tear-free dotted line that is easy to rip off. You can give as a customer copy or keep for record keeping. We've provided extra rows on the back for additional note taking.Perfect For Restaurants, Lounges, Hotels, Cafes, And Waiters To Use.
- Record Important Information: These server note pads can record important information.Each ticket has a unique serial number printed at the top, dates, order details, number of guests, order amount, table numbers etc. They are lightweight, small and can fit most aprons. They can be used on-demand and can help decrease errors in orders, while improving work efficiency.
- High Quality: Sturdy, Not Drop Powder, It's Thick, You Can Write On The Back And Front Easily.Their whole page printing has clear handwriting and a reasonable layout. On the customer retention part of each guest check, "THANK YOU" on the back to make customers feel appreciated.
- Contact Us: We're confident that the quality of the server note pads will go beyond your expectation. If you experience an issue, feel free to contact us, we'll appreciate it to learn from your experience, and we'll make it better
Where do I create reverse DNS for a VPS?
Use the company that owns the IP address: its VPS panel, an rDNS/PTR page, or a support ticket. The registrar or DNS provider hosting your normal domain zone cannot set a PTR for an address it does not control.
Why does my PTR still show the provider hostname?
The custom value may not have been submitted, may have been applied to another address, or may still be within the provider’s change window. Recheck the exact IP, confirm the complete FQDN, and ask support to verify the reverse-zone entry.
Does an IPv4 PTR also cover IPv6?
No. IPv4 uses a name beneath in-addr.arpa; IPv6 uses ip6.arpa. Set an IPv6 PTR separately and publish an AAAA record that resolves back to the same IPv6 address.
What should I do if a provider rejects my PTR hostname?
Publish the matching A or AAAA record first, wait until the authoritative DNS server answers, and submit the complete FQDN again. Check that it does not point to an internal or unrelated address and contains no URL or malformed text.
Do multiple PTR records provide round-robin reverse DNS?
They are unsupported or unreliable for this use. Keep one canonical PTR per address. If separate reverse identities are required, use separate public addresses or a delegated reverse zone.
Recommended Free Tools
How many IPs do I need for three domains?
You need only one address if the domains can share one reverse identity. You need three addresses only when each domain or service must independently reverse-resolve to its own hostname. Additional addresses may incur charges and provider approval.
Is a delegated reverse zone necessary for one VPS?
No. Delegation is intended for customers controlling a sufficiently large block and willing to operate authoritative reverse DNS. For one or a few addresses, provider-managed PTR fields or support requests are simpler.
The Bottom Line
One public IP normally means one PTR hostname, regardless of how many domains the VPS hosts. Publish a matching A or AAAA record, set the PTR through the IP owner, verify both directions with dig, and configure IPv4 and IPv6 separately. Use additional addresses or delegated reverse space only when a service genuinely requires distinct reverse identities.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
