Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

VPS & Linux

VPS reverse DNS: how PTR records, forward DNS and mail identity fit together

Published August 2026 · 2 min read · Updated 2026-09-05

Reverse DNS maps an IP address back to a hostname through PTR records controlled by the address owner or provider. It is most important when a service’s identity is evaluated against its public address, especially mail, logging, abuse handling, and some allowlists.

Choose a stable hostname for the address

Use a hostname you control and intend to keep with the server or service role. Publish forward A or AAAA data so the hostname resolves back to the same address when forward-confirmed reverse DNS is expected.

Avoid assigning a customer website hostname as infrastructure identity if that name may move independently.

Set PTR through the provider that owns the IP

Adding a PTR-looking record to your ordinary DNS zone does not change reverse DNS for a provider-owned address. Use the provider control plane or support process for the reverse zone.

Allow for propagation, then query the relevant in-addr.arpa or ip6.arpa name directly.

Align mail identity deliberately

For SMTP, the PTR, forward record, server hostname, EHLO/HELO, and actual outbound source IP should form a coherent identity. SPF/DKIM/DMARC solve different authorization and alignment questions and still need correct configuration.

Reverse DNS alone does not guarantee inbox placement or reputation.

Recheck after address changes

When a VPS is rebuilt or receives a new public IP, update forward DNS, PTR, service configuration, monitoring, and allowlists together. Remove stale identity from the old address if it returns to a pool.

  • Choose a stable infrastructure hostname.
  • Set PTR at the IP provider.
  • Verify forward and reverse alignment.
  • Reconcile identity when addresses change.

Next step

Set and verify reverse DNS for a VPS, understand provider-controlled PTR records, and keep forward DNS and service identity consistent where it matters.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move