Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
You cannot normally create a separate PTR record for every domain on one public IP address. A PTR belongs to an IP address, and the organization that owns that address—usually your VPS provider—controls its reverse-DNS zone. Give each address one stable canonical hostname, create matching A and AAAA records for that hostname, then set the PTR through the provider’s panel or support process. If each domain needs a different reverse identity, assign separate public IP addresses or obtain delegated reverse-DNS space.
What a PTR record does
A PTR (pointer) record performs the opposite job of the familiar forward DNS records. An A record answers “Which IPv4 address belongs to this hostname?” An AAAA record answers the same question for IPv6. A PTR answers “Which hostname is associated with this IP address?”
Reverse lookups use special DNS namespaces: in-addr.arpa for IPv4 and ip6.arpa for IPv6. For example, a lookup of 203.0.113.10 queries a name under 10.113.0.203.in-addr.arpa. A normal authoritative zone for example-a.com cannot answer that query, even if you administer the domain.
The reverse zone is normally delegated to the owner of the IP address. On a VPS, that is generally the hosting provider or its upstream network. Your domain registrar controls your forward zone; it does not automatically control reverse DNS for a rented address.
#1 Best Overall
Can several domains share one VPS and one PTR?
Yes. Websites, applications and mail services for several domains can use the same VPS and public IP. They share the IP’s single reverse-DNS identity. If 203.0.113.10 serves example-a.com, example-b.com and example-c.com, choose one canonical fully qualified domain name (FQDN), such as mail.example-a.com or vps1.example-a.com, and set the PTR for 203.0.113.10 to that name.
The other domains still have their own forward records and can be configured as virtual hosts or mail domains. They do not receive additional PTR values on that same address. A provider may reject multiple PTR values, and resolvers or receiving mail systems may select an arbitrary value if a technically invalid configuration is accepted.
| Requirement | One shared IP | Separate IPs |
|---|---|---|
| Websites for multiple domains | Supported with virtual hosting | Supported |
| PTR identities | One effective hostname for the IP | One hostname per IP |
| Forward DNS | Each domain can have its own A/AAAA records | Each hostname points to its assigned address |
| Mail-server identity | All senders share the address’s reverse identity | Each sending identity can have its own reverse name |
| Provider action | Set one PTR in the reverse-DNS control | Set one PTR for every address |
Choose the canonical hostname before changing DNS
Select a name that will remain valid even if you add or remove hosted domains. A service-oriented name is usually easier to maintain than choosing whichever customer domain happens to be first on the server.
- For a mail server: use a name such as
mail.example-a.comand make it the server’s SMTP greeting and TLS name where applicable. - For a general VPS: use a stable host name such as
vps1.example-a.com. - For multiple outbound services: assign one canonical name per originating address, rather than attempting to encode every domain in one PTR.
The hostname must be an FQDN that you control. Avoid pointing a PTR at a name that will expire, be transferred, or later point to a different system. Decide whether the name should identify the machine (vps1) or a principal service (mail) and use that choice consistently in forward DNS, operating-system configuration and application settings.
Rank #2
- Linux
- Linux DNS
Step-by-step: set a PTR for an IPv4 or IPv6 address
- Inventory every address that will originate traffic. Record each public IPv4 and IPv6 address assigned to the VPS. Include addresses used by SMTP, APIs, monitoring agents, webhooks and other outbound services. A multi-homed host should have reverse data for every address, not just its primary address.
- Assign one canonical FQDN to each address. If one address is shared by all services, select one name. If the VPS has several addresses, map each address to a distinct stable name, such as
mail4.example-a.comfor IPv4 andmail6.example-a.comfor IPv6. - Create the forward record first. In the authoritative DNS zone for the chosen hostname, create an A record for IPv4 or an AAAA record for IPv6. Point it to the exact public address. For example:
mail.example-a.com. IN A 203.0.113.10
mail6.example-a.com. IN AAAA 2001:db8::10- Set reverse DNS with the IP owner. Open the VPS provider’s networking or reverse-DNS page. Common labels include “rDNS,” “Reverse DNS,” “PTR,” or “Edit hostname.” Enter the address and the exact FQDN. If there is no self-service field, submit a support request containing the IP address and requested hostname. Do not add the PTR to the forward zone for
example-a.com. - Observe the provider’s change window. Reverse-DNS updates are controlled by the address owner. The panel may apply the change immediately, or support may process it during a stated window. Record any provider-specified TTL or propagation interval; there is no universal update time.
- Verify the reverse result. Query the address directly:
dig -x 203.0.113.10 +short
dig -x 2001:db8::10 +shortThe first command should return the selected IPv4 hostname and the second should return the selected IPv6 hostname. A trailing dot in output, such as mail.example-a.com., is normal DNS presentation.
- Confirm the forward direction. Query the names you created:
dig mail.example-a.com A +short
dig mail6.example-a.com AAAA +shortThe returned address must match the address whose PTR you set. Repeat the reverse and forward checks from a second network or recursive resolver if you need to distinguish local caching from an uncommitted provider change.
Forward-confirmed reverse DNS (FCrDNS)
A reliable configuration forms a loop: the IP’s PTR returns a hostname, and that hostname’s A or AAAA record returns the same IP. This is commonly called forward-confirmed reverse DNS (FCrDNS). RFC 1912 section 2.1 states that every IP address should have a matching PTR in the appropriate reverse namespace and that all addresses on a multi-homed host should be covered.
FCrDNS does not make the PTR unique to every hosted domain; it simply proves that the chosen identity is under your DNS control and points back to the originating address. Mail operators often use this consistency check as one signal among many. It cannot by itself overcome poor sender reputation, missing authentication or an address policy that blocks outbound mail.
When each domain really needs its own reverse identity
If operational or mail-policy requirements demand a different PTR hostname for each domain, give each identity a different public IP. For example:
| Address | PTR hostname | Forward record | Typical use |
|---|---|---|---|
203.0.113.10 |
mail-a.example-a.com |
A record to 203.0.113.10 |
Mail for example-a.com |
203.0.113.11 |
mail-b.example-b.com |
A record to 203.0.113.11 |
Mail for example-b.com |
2001:db8::10 |
mail6-a.example-a.com |
AAAA record to 2001:db8::10 |
IPv6 mail for example-a.com |
Ask the provider whether additional IPv4 addresses are available, whether IPv6 addresses can be assigned individually, and whether each address can receive a custom PTR. An address that exists on the server but cannot have reverse DNS set may not satisfy your mail or compliance design.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDelegated reverse zones for larger address blocks
Customers with a sufficiently large routed block may be able to manage the reverse zone themselves. The IP owner delegates authority for part of the reverse namespace to your DNS servers, after which you publish PTR records in that delegated zone.
For classless IPv4 allocations, RFC 2317 describes the reverse-zone delegation technique. IPv6 reverse zones use the hexadecimal-nibble structure under ip6.arpa; providers document the exact delegation and zone names for their allocation. The provider must explicitly delegate the block—owning several addresses on a VPS does not automatically grant authority over their reverse zone.
Delegation is appropriate when you operate many addresses and need independent change control. For a handful of VPS addresses, provider-managed PTR fields are simpler and less error-prone. Before requesting delegation, confirm the required prefix size, authoritative nameserver availability, DNSSEC expectations and the provider’s procedure for creating the parent delegation.
Where to create reverse DNS on a VPS
Look in the infrastructure provider’s network, IP-address or instance settings rather than in your domain registrar. The available workflow usually falls into one of these patterns:
| Provider workflow | What you do | What to verify |
|---|---|---|
| Self-service per address | Open the instance or IP page, enter an FQDN and save | Both IPv4 and IPv6 appear as editable addresses |
| Support-mediated | Send the IP and requested FQDN in a ticket | Policy, processing time and change limits |
| Delegated reverse zone | Provide nameservers and publish PTRs yourself | Prefix eligibility and parent-zone delegation |
| No custom reverse DNS | Use the provider-assigned hostname or move the originating service | Whether outbound SMTP is permitted at all |
Check these points before purchasing addresses or deploying a mail service:
- Custom PTR support for both IPv4 and IPv6.
- Whether additional addresses can be ordered and routed to the same VPS.
- Whether the provider requires forward DNS before accepting a PTR change.
- Outbound email restrictions, abuse procedures and port-25 policy.
- Whether addresses can be moved between instances without losing their reverse settings.
Common failures and precise fixes
The lookup still returns the provider hostname
Your custom value may not have been saved, may still be propagating, or may have been entered for a different address. Reopen the provider’s IP page, compare the address character by character, and query with dig -x <address> +short from outside the VPS. If the panel shows the custom name but public resolvers do not, ask support for the change status and the applicable TTL or update window.
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
A PTR was added to the domain’s DNS zone
That record is in the wrong namespace. Remove the misplaced entry and create the A or AAAA record in the forward zone instead. Submit the PTR through the IP owner or use a delegated reverse zone if one has been assigned to you.
Several PTR values were entered for one address
Replace them with one canonical hostname. The normal provider model is one IP-to-one-PTR, and provider documentation may reject additional values. If distinct identities are essential, request separate addresses rather than publishing competing PTRs.
The PTR hostname has no matching A or AAAA record
Create the forward record first or correct it to the exact address. Check both record type and address family: an IPv4 PTR must resolve through an A record, while an IPv6 PTR should resolve through an AAAA record. Query both directions after DNS caches expire.
IPv4 works but IPv6 mail fails
Mail software may prefer IPv6 whenever an AAAA route exists. Give the IPv6 address its own PTR and matching AAAA record, and ensure the VPS firewall, routing, SMTP configuration and provider policy all support IPv6. If IPv6 is not fully configured, remove the public AAAA path or configure the application to use a correctly identified address rather than allowing half-configured delivery.
The provider will not set a custom PTR
This is a policy limitation, not a syntax error in your domain zone. Use the assigned hostname, select a provider that offers customer-controlled reverse DNS, or move the outbound service to an address with appropriate rDNS control. Do not attempt to override the provider’s reverse zone from your own nameservers.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →PTR records and multiple-domain email
SMTP uses the sending IP as a network identity, so all domains sending from one shared address present the same PTR hostname. That is compatible with hosting multiple domains, but it means the reverse name should describe the server or mail service rather than pretending to represent every domain simultaneously.
Configure each domain’s forward and mail records separately, and align the SMTP server’s banner and TLS certificate with the canonical hostname where your mail software supports those settings. Also configure the domain-level authentication and policy records required by your mail design, such as SPF, DKIM and DMARC. A matching PTR is one part of deliverability; it is not a substitute for those controls, sound list practices or a clean sending reputation.
If different customers or organizations must have isolated reverse identities, separate addresses are the clear boundary. Document which domain uses which source address so that a later application change does not silently send from an address whose PTR describes another service.
Quick Recap
Operational checklist for changes
- List all public IPv4 and IPv6 addresses currently assigned to the VPS.
- Map every outbound service to the address it actually uses.
- Choose one durable FQDN per address.
- Publish matching A and AAAA records before requesting reverse changes.
- Set the PTR with the address owner, not the domain registrar.
- Verify with
dig -xand forwarddigqueries from more than one resolver when timing matters. - Check mail software, greetings, certificates and firewall rules after changing an address or hostname.
- Keep a record of provider policy, processing time and the address-to-hostname mapping.
Decision guide
| Your situation | Recommended design |
|---|---|
| Several websites, one VPS, no separate mail identities | Keep one shared IP and set one stable PTR hostname. |
| Several mail domains using one outbound service | Use one canonical mail hostname for the shared IP; configure each domain’s forward and authentication records separately. |
| Each domain must have a distinct reverse identity | Assign one public IP per identity and set one PTR for each. |
| Many addresses with in-house DNS operations | Request reverse-zone delegation and publish PTRs in the delegated zone. |
| Provider offers no custom rDNS | Use its hostname or choose an address/provider with documented reverse-DNS control. |
Key points
- A PTR maps an IP address to a hostname through
in-addr.arpaorip6.arpa. - The IP owner, normally the VPS provider, controls the reverse zone.
- One public IP normally has one effective PTR hostname, even when many domains share the server.
- Every PTR should be forward-confirmed by a matching A or AAAA record.
- Separate PTR identities require separate public IPs or an explicitly delegated reverse block.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
