Home/HighLevel/Features/Email/How to set up reverse DNS (PTR) for a dedicated IP in HighLevel

Conversations and Inbox

How to set up reverse DNS (PTR) for a dedicated IP in HighLevel

In short

Reverse DNS (PTR) links a dedicated IP to a hostname you own. In HighLevel this lets mailbox providers display your company name instead of a third party label, boosting trust and inbox placement. The setup requires an A record and updates inside Agency Settings.

AreaEmail · LC Email
Used forDigital marketing agency, SaaS startup, Online retailer
Setup steps5 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Marketing agencies that send client newsletters benefit because the sender field shows their own brand, not an email service name.
  • SaaS companies running automated onboarding emails gain consistent branding and higher trust when the company name appears as sender.
  • Ecommerce retailers sending order confirmations improve perceived legitimacy by showing their store name in the sender field.

02Reverse DNS white labeling, explained

Reverse DNS translates an IP address back to a hostname. When a mailbox provider looks up the IP used to send your email, the returned hostname determines what appears in the technical sender details. Setting up a PTR record therefore lets your company name show instead of a third party service.

In HighLevel the rDNS feature is available only for dedicated IPs. You access it through Agency Settings > Email Service, then open the Dedicated Domain And IP panel in the SMTP Service tab. From the list of dedicated IPs you choose the three dot menu and select Reverse DNS (PTR) to enter your hostname.

The result is consistent branding across all campaigns. Recipients see your own domain or subdomain as the sender, which can increase trust and improve inbox placement.

03How businesses use reverse DNS white labeling

  • Digital marketing agency. The agency creates an A record for a subdomain like mail.agency.com pointing to its dedicated IP. Then it follows the HighLevel steps to add that hostname as the PTR record, ensuring client newsletters show the agency’s name as sender.
  • SaaS startup. The startup adds an A record for mail.appdomain.com that resolves to its dedicated IP. Inside HighLevel it navigates to the Reverse DNS (PTR) setting and enters mail.appdomain.com, so onboarding emails display the app’s brand.
  • Online retailer. The retailer sets up an A record for mail.shopdomain.com targeting its dedicated IP. Using the Dedicated Domain And IP screen in HighLevel, it configures the PTR with that hostname so order confirmations carry the store’s name.

04The numbers and rules that matter

  • Shared IPs do not support rDNS because they resolve to only one hostname per IP address.
  • Propagation of PTR updates can take from a few minutes up to 48 hours depending on TTL.

05Before you start

  • A dedicated IP must be assigned to your account in HighLevel.
  • Access to your DNS hosting provider to create an A record that points a hostname to the dedicated IP.

06How to set up and use reverse DNS white labeling in HighLevel

Configure reverse DNS (PTR) for a dedicated IP

  1. Add an A record at your DNS hosting provider that points the chosen hostname to your dedicated IP address.
  2. Open Agency Settings and select Email Service.
  3. In the SMTP Service tab click Dedicated Domain And IP in the LeadConnector section.
  4. Click the three dot menu next to your dedicated IP and choose Reverse DNS (PTR).
  5. Enter the hostname you used in the A record and save the PTR configuration.

07What it looks like in HighLevel

08Settings that matter

  • Reverse DNS (PTR). Specifies the hostname that the dedicated IP will resolve to when mailbox providers perform a reverse DNS lookup.
  • Dedicated Domain And IP. Opens the panel where you manage the domain and IP pair, including access to the reverse DNS (PTR) option.

09Things to know before you rely on it

  • rDNS can only be set on a dedicated IP; shared IPs do not support it.
  • The PTR record must return a valid hostname, and that hostname’s A record must resolve back to the same IP.
  • If the hostname does not resolve, mailbox providers may flag the email as suspicious.

10If something goes wrong

  • Incorrect or missing PTR record. Create a correct PTR record that points the dedicated IP to a valid hostname.
  • Mismatched hostname (forward confirmed rDNS failure). Ensure the hostname returned by the PTR resolves back to the same dedicated IP.
  • Hostname does not resolve. Verify the A record for the hostname exists and correctly points to the dedicated IP before submitting the PTR.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Reverse DNS white labeling feels like a small convenience that can quickly shift how your emails are perceived. By moving the sender name from a generic service to your own brand, you get a cleaner inbox presence without changing your workflow.

A boutique agency that sends client newsletters will see the benefit. The agency can point a subdomain like mail.myagency.com to its dedicated IP, set the PTR record, and let every client email carry the agency’s name instead of the service provider’s tag.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about reverse DNS white labeling.

Can I set up rDNS on a shared IP?

No. rDNS resolves to only one hostname per IP address, so it is supported only on dedicated IPs.

What is a PTR record and why does it matter?

A PTR (Pointer) record maps an IP address back to a hostname. Mailbox providers use it to verify that the sending server is legitimate, and missing or incorrect records can cause email rejection.

How long does rDNS propagation take?

Updates to the PTR record are applied quickly on the back end, but full DNS propagation can take from a few minutes up to 48 hours depending on TTL settings.

How can I verify that my rDNS is set up correctly?

Run a reverse DNS lookup on your dedicated IP with a tool like MXToolbox or a command line query. The result should return the hostname you configured, and a forward lookup of that hostname should resolve back to the same IP.

Does rDNS replace DKIM or SPF authentication?

No. rDNS, DKIM, and SPF each serve different purposes. rDNS verifies the sending server’s identity, DKIM signs the email content, and SPF authorizes the sending IPs.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.