You can host many domains on one VPS, but one public IP normally has one effective PTR hostname. Set reverse DNS for that IP through the organization that owns the address—usually your VPS provider—not in any domain’s ordinary DNS zone. Choose one canonical fully qualified domain name (FQDN), point its A or AAAA record to the IP, set the IP’s PTR to that FQDN, and verify that forward and reverse lookups agree. Separate PTR identities require separate public IP addresses or a delegated reverse-DNS block.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What a PTR record does
A PTR (pointer) record performs the opposite mapping of the familiar A and AAAA records. An A record maps a hostname to an IPv4 address; an AAAA record maps a hostname to an IPv6 address. A PTR maps an address back to a hostname. This is called reverse DNS (rDNS).
As an Amazon Associate I earn from qualifying purchases.
Reverse lookups use special namespaces: IPv4 addresses are queried below in-addr.arpa, while IPv6 addresses are queried below ip6.arpa. A request for the PTR of 203.0.113.10, for example, is sent to the reverse zone for that address, not to the authoritative DNS servers for example-a.com. Adding a PTR record inside the forward zone for a domain therefore has no effect on reverse lookups.
The reverse zone is normally controlled by the address holder. For a rented VPS, that is the hosting or network provider. The provider may expose a reverse-DNS field in its control panel, or it may require a support request. Your registrar and the DNS provider that hosts your normal domain zone generally cannot change a VPS address’s PTR.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Can every domain on one VPS have its own PTR?
Not with the normal one-address provider model. A single public IP has one authoritative reverse-DNS identity. If 203.0.113.10 serves three sites, the address can point to one canonical name such as mail.example-a.com or server1.example-a.com. example-b.com and example-c.com can still run websites, APIs, and mail services on that machine, but they share the address’s PTR identity.
DNS software can technically return multiple PTR records, but major address owners commonly reject or do not support that configuration. Operationally, clients that expect a single reverse name may choose one value unpredictably, and mail systems may treat the result as misconfigured. Treat one IP-to-one-PTR as the supported rule unless your address provider explicitly documents another arrangement.
| Requirement | Suitable design | What the domains share |
|---|---|---|
| Several websites, one server identity | One IP, one canonical PTR | The websites share the IP’s reverse name |
| Several mail domains using one outbound address | One IP, one stable mail/server hostname as PTR | All outbound connections present the same reverse identity |
| Each domain must have a distinct reverse identity | One public IP per identity | Nothing; each address can have its own PTR |
| Many addresses under your own control | Provider-delegated reverse zone or classless reverse delegation | You manage PTR data for the delegated range |
Plan the address and hostname layout
Inventory every address that will originate traffic
List all public IPv4 addresses and IPv6 addresses used by the VPS. Include addresses assigned to additional interfaces, virtual machines, containers, NAT gateways, and dedicated mail services. A multi-homed host should have corresponding PTR data for each address that can appear as a source. Do not configure only the first address and assume the rest inherit its reverse name.
Record each address in a change sheet with its interface, purpose, region, and provider account. This prevents a later migration from leaving an old address pointing at a hostname that now resolves elsewhere.
Choose one canonical FQDN for each address
Select a stable name that identifies the service using the address. A mail-oriented name such as mail.example-a.com is common when the address primarily sends email; a neutral name such as vps1.example-a.com works for mixed workloads. The name should remain valid if you add or remove hosted domains.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Avoid using a temporary provider hostname if you intend to move providers, and avoid naming the address after a single customer domain when many unrelated domains depend on it. PTR is an infrastructure identity, not a list of every virtual host on the server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Create forward DNS before reverse DNS
In the authoritative forward zone for the chosen name, create an A record for IPv4 or an AAAA record for IPv6 that points to the exact address. For example:
mail.example-a.com A 203.0.113.10mail.example-a.com AAAA 2001:db8::10
Use the same FQDN, spelling, and address in the provider’s reverse-DNS field. Many providers validate forward resolution before accepting a PTR change; even when they do not, forward-confirmed reverse DNS is expected by many receiving mail systems.
Set the PTR through your VPS provider
- Open the address-management area. Sign in to the VPS control panel and look under networking, IP addresses, reverse DNS, or rDNS. The label varies by provider. If no field exists, locate the provider’s support channel and ask whether custom PTR records are available for your specific IPv4 and IPv6 addresses.
- Enter the exact address and FQDN. Select one address, enter the canonical hostname as a fully qualified name, and save. Do not enter a domain apex unless that is deliberately the hostname you created;
example-a.comandmail.example-a.comare different names. - For a support ticket, include complete data. Provide the IP address, requested PTR hostname, confirmation that the A or AAAA record already resolves to that address, and the server or account identifier. Submit one request per address if the provider’s process requires it.
- Repeat for IPv6. IPv4 and IPv6 reverse zones are independent. Setting the IPv4 PTR does not set the IPv6 PTR, so submit the IPv6 address and its matching AAAA hostname separately.
- Wait for the provider’s change window. The update interval and TTL are provider-specific. Keep the provider’s stated timing with your deployment record and do not repeatedly submit conflicting values while an earlier change is pending.
If the panel keeps reverting to a provider hostname, the address may be using a mandatory default, may not be eligible for custom rDNS, or may be controlled by a different account than the VPS. Contact the address owner rather than changing your domain’s nameservers.
Verify both directions from outside the VPS
Verification should be performed from a resolver that is not relying solely on the server’s local cache. The dig utility is available on most Linux and macOS systems; equivalent DNS tools can be used elsewhere.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Query the IPv4 PTR:
dig -x 203.0.113.10 +short. The output should be the canonical FQDN, normally with a trailing dot. - Query the forward A record:
dig mail.example-a.com A +short. Confirm that203.0.113.10appears. - Query the IPv6 PTR:
dig -x 2001:db8::10 +short. - Query the matching AAAA record:
dig mail.example-a.com AAAA +short. Confirm that2001:db8::10appears. - Repeat the checks using more than one recursive resolver if a change appears inconsistent. A cached answer can persist until its TTL expires.
The important test is forward confirmation: the PTR name must resolve back to the same address that produced the reverse answer. If the PTR says mail.example-a.com but the A record points to a different server, correct the forward record or the PTR before sending production traffic.
Handling several domains on the same VPS
Websites and APIs
HTTP hostnames are selected by the Host header or TLS SNI, so multiple sites can share one address without separate PTR records. Configure each site’s A and, where applicable, AAAA record to the VPS address. The web server then routes requests by hostname. Reverse DNS is not the mechanism that chooses a website.
Mail for multiple domains
All outbound SMTP connections sourced from one address present that address’s single reverse identity. Configure the mail server’s announced hostname to match the canonical PTR where practical, and publish matching forward DNS. Each sending domain still needs its own normal email-authentication records and policy, but those records do not create additional PTRs. If reputation, isolation, or customer policy requires a distinct reverse identity, assign a separate source IP and set a separate PTR for it.
Containers, guests, and source-address selection
Containers and virtual machines may use private addresses while the host performs NAT, in which case external recipients see the host’s public address and its PTR. If a guest has its own public address, treat it as a separate inventory item and configure its reverse record independently. Confirm which source address applications actually select, especially on dual-stack systems; an application using IPv6 will be evaluated against the IPv6 PTR, not the IPv4 one.
When separate PTR identities are genuinely required
Assign additional public addresses
Request additional IPv4 or IPv6 addresses from the provider and allocate one address to each identity that needs independent reverse DNS. For every address, create its forward A or AAAA record, set one PTR through the address owner, and verify the pair. Ask about allocation fees, routing, abuse limits, and whether the extra addresses can be used for mail before committing to the design.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Use a delegated reverse zone for a block
If you control a sufficiently large address range, the network owner can delegate the reverse zone to your authoritative DNS servers. Classless IPv4 delegation is described by RFC 2317; IPv6 providers use analogous delegation methods under ip6.arpa. Delegation lets you manage many PTR records, but it does not make multiple PTRs valid for one address. Each address in the delegated range still receives its own hostname.
Delegation adds operational responsibility: your nameservers must be reachable, authoritative, and redundant, and the delegation must match the exact range supplied by the network owner. A single VPS customer with a few addresses usually needs provider-managed PTR fields rather than a delegated zone.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCommon failures and precise fixes
| Symptom | Likely cause | Fix |
|---|---|---|
dig -x returns the provider hostname |
The provider’s default PTR is still active, or custom rDNS is unavailable | Check the address panel and provider policy; request the change from the IP owner |
You added a PTR in example-a.com, but reverse lookup is unchanged |
PTR belongs to in-addr.arpa or ip6.arpa, not the forward zone |
Remove the ineffective record and set reverse DNS through the provider |
| Several PTR values appear intermittently | Multiple values were published or cached across servers | Use one supported PTR value and ask the provider to remove extras |
| PTR resolves, but mail checks still fail | The PTR hostname’s A or AAAA record does not return the sending address | Correct forward DNS, wait for caches to expire, then retest both directions |
| IPv4 passes but IPv6 fails | No IPv6 PTR was configured, or the AAAA record is missing or mismatched | Configure and verify the IPv6 pair separately, or disable unintended IPv6 sending |
| The panel rejects the hostname | The name is not fully qualified, has a typo, or does not yet resolve forward | Use the exact FQDN and create the matching A or AAAA record first |
| Changes are visible from one resolver but not another | Recursive caches still hold the previous TTL | Wait for the published TTL and query multiple external resolvers |
How to evaluate a VPS provider for reverse DNS
Reverse-DNS support should be checked before purchasing an address or moving a mail workload. Ask these questions in writing:
| Evaluation point | Why it matters |
|---|---|
| Is custom PTR self-service or support-mediated? | Self-service is faster; support-only workflows require a documented ticket path and change window. |
| Are IPv4 and IPv6 both supported? | A dual-stack server can fail reputation checks if only its IPv4 address has a PTR. |
| Can additional addresses be ordered? | Separate identities require separate public addresses. |
| Is reverse-zone delegation available for eligible blocks? | Delegation is useful when you must manage many addresses yourself. |
| Is forward confirmation enforced? | Validation prevents a PTR from pointing at a hostname that resolves elsewhere. |
| What email and abuse policies apply? | Some providers restrict SMTP, require approval, or reclaim addresses after abuse complaints. |
| What happens during reassignment? | A released address may retain old reverse data until the next customer changes it; document the provider’s cleanup process. |
Operational practices after the initial setup
Keep an address-to-hostname inventory
Store each IP, PTR hostname, A or AAAA record, server role, and responsible team in the same inventory. Update it whenever an address is added, removed, or moved. This makes migrations safer and exposes stale reverse names before they affect mail or monitoring.
Monitor forward and reverse consistency
Schedule periodic checks that perform both dig -x and a forward query for every production address. Alert when the PTR changes unexpectedly, when the hostname stops resolving, or when it resolves to a different address. Monitoring from outside your network catches provider-side changes that local DNS may hide.
Change one side at a time during migration
Before moving a service, create the new hostname’s forward record and confirm it. Change the provider PTR only when the new address is ready to serve traffic, then verify from external resolvers. During a staged migration, keep each address’s PTR aligned with the service actually using it rather than pointing old and new addresses at one name without a plan.
Account for cached data
PTR changes are not instantaneous. Recursive resolvers retain old answers until their TTL expires, and remote mail systems may cache the old identity longer in their own policy engines. Plan changes outside critical sending windows and retain the previous configuration until external checks show the new value consistently.
Worked example: three domains, one IPv4 address
Suppose a VPS hosts example-a.com, example-b.com, and example-c.com on 203.0.113.10. Choose mail.example-a.com as the infrastructure hostname. In the forward zone, publish mail.example-a.com A 203.0.113.10, along with the web records required by each domain. In the VPS panel, set the PTR for 203.0.113.10 to mail.example-a.com. A reverse query then returns that one name, while web requests for all three domains continue to route through their own hostnames.
If example-b.com later needs an independent mail identity, obtain another public address such as 203.0.113.11. Publish mail.example-b.com A 203.0.113.11, set that address’s PTR to the same hostname, and configure the mail service to use 203.0.113.11 when sending for that identity. The original address keeps its existing reverse name.
Deployment checklist
- List every public IPv4 and IPv6 address that can originate traffic.
- Choose one durable canonical FQDN for each address.
- Create and verify the matching A or AAAA record first.
- Set the PTR with the IP owner through its panel or support process.
- Configure IPv4 and IPv6 reverse DNS separately.
- Run
dig -xand forward queries from outside the VPS. - Confirm that each PTR hostname resolves to the same address.
- Use additional addresses or delegated reverse space when distinct identities are mandatory.
- Record provider TTLs, policies, and change windows in your inventory.
- Monitor for unexpected PTR changes and stale forward records.
Bottom line
Multiple domains can share one VPS and one public IP, but they share that IP’s single supported PTR identity. Put normal A and AAAA records in your domain zones, put the PTR in the address owner’s reverse-DNS system, and keep the two directions consistent. Only separate public addresses—or a properly delegated reverse block—provide separate PTR identities.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
