- Journey Optimizer documentation
- What’s new?
- Get started
- Journeys
- Campaigns
- Conflict management & prioritization
- Test & approve
- Communication channels
- Get started with communication channels
- Email channel
- In-app channel
- Push notification channel
- SMS / MMS channel
- Direct mail
- Web channel
- Code-based experience
- Content cards
- Landing pages
- Content management
- AI Assistant for content generation
- Work with Multilingual content
- Work with Content experiment
- Personalization
- Content templates
- Reusable content fragments
- Dynamic content
- Audiences, profiles & identity
- Integrations
- Track & monitor
- Live report
- All time report
- Journey reports
- Deliverability
- Alerts
- Exclusion reasons
- Decision capabilities
- Get started with decision capabilities
- Decisioning
- Get started with Decisioning
- Decisioning guardrails & limitations
- API reference
- Manage decision items
- Configure item selection
- Create selection strategies
- Create decision policies
- Report on Decisioning
- Decisioning use case
- Decision management
- Get started with Decision management
- Create components
- Create rankings
- Create & manage offers
- Create & manage decisions
- Use batch decisioning
- Collect event data
- Leverage context data
- Create Decision Management reports
- Export your offer catalog
- API Reference
- Getting started
- Create & manage offers using APIs
- Deliver offers using APIs
- Data management
- Channel configuration
- Journey configuration
- Connect your systems and environments
- Access control
- Privacy
Create & edit PTR records
About PTR records
A pointer record (PTR) is a type of Domain Name System (DNS) record that provides the domain name linked to an IP address.
With PTR records, receiving mail servers can check the authenticity of sending mail servers by identifying whether their IP addresses correspond to the names that the servers connect to.
Access your subdomains’ PTR records
Once you delegate your first subdomain to Adobe in Journey Optimizer, PTR records are automatically created for your IPs. You can access them from the Administration > Channels > Email settings > PTR records menu.
The list shows the PTR records generated using the syntax below:
- “r” for record,
- “xx” for the two last figures of the IP address,
- subdomain name.
You can open a PTR record from the list to display the associated subdomain name and IP address.
Edit a PTR record
In Journey Optimizer, you cannot manually create PTR records. Instead, once you delegate your first subdomain to Adobe, PTR records are automatically created for your IPs.
Each of your IPs receives a single PTR record. All PTR records have the following format: ‘rxx.subdomain’, where ‘subdomain’ is the first subdomain you delegated in Journey Optimizer.
When you create additional subdomains, you need to modify one or more of the PTR records and assign that new subdomains to them. To do so, follow the steps below.
PTR records are common to all environments. Therefore any modification to an PTR record will also impact the production sandboxes.
Proceed with extra care when editing PTR records. In case of any doubt, contact a deliverability expert.
Fully delegated subdomains
To edit a PTR record with a subdomain that is fully delegated to Adobe, follow the steps below.
-
From the list, click a PTR record name to open it.
-
Select a subdomain fully delegated to Adobe from the list.
-
Click Save to confirm your changes.
You cannot modify the IP and PTR record fields.
Delegated subdomains using the CNAME method
To edit a PTR record with a subdomain that is delegated to Adobe using the CNAME method, follow the steps below.
-
From the list, click a PTR record name to open it.
-
Select a subdomain delegated to Adobe using the CNAME method from the list.
-
You need to create a new forward DNS record on your hosting platform. To do this, copy the record generated by Adobe. Once done, check the box “I confirm…”.
NOTEIf you get this message: “Please create forward DNS first and then try again”, follow the steps below:
- Check on the DNS provider if the forward DNS record was successfully created.
- Records across the DNS may not synchronize immediately. Wait for a few minutes, and try again.
-
Click Save to confirm your changes.
You cannot modify the IP and PTR record fields.
Check PTR record update details
Once you confirmed the PTR record edit, the Processing icon displays next to the name of the PTR record in the list.
The update processing can take up to 3 hours.
To check the PTR record update details, click the icon next to it. Learn more about the statuses associated with the different icons in this section.
You can see information such as the update status, and the requested changes.
PTR record update statuses
A PTR record update can have the following statuses:
Processing: The PTR record update has been submitted and is going through a verification process.
Success: The updated PTR record has been verified and the new subdomain is now associated with the IP address.
Failed: One or several checks have failed during the PTR record update verification.
Processing
Several deliverability checks will be performed to verify that the new subdomain to associate with the IP address is valid. This can take up to 3 hours.
You cannot modify a PTR record while update is in progress. You can still click its name, but the Subdomain field is greyed out. The changes will not be reflected until the update is successful.
During the validation process, the old subdomain is still associated with the IP address.
Success
Once the validation process is successful, the new subdomain is automatically associated with the IP address.
Failed
If the validation process fails, the older PTR record is displayed. The valid subdomain that was previously associated with the IP address remains unchanged.
The possible update error types are as follows:
- Failure to create a new forward DNS for the PTR record
- Failure to update the record
- Failure to re-onboard the affinities
Upon update failing, the PTR record becomes editable again. You can click its name and update the subdomain again.
