DNS Settings for Customer Sites

When setting up the site for a customer they will need to configure a number of DNS entries before they can start using their system.

Main Host Name

This will be the name of the site that will point to the iPro servers.  If they are using our web servers it will be something like www.example.com.  If they are using their own web site it will be something like secure.example.com or booking.example.com.  This needs to be created as an A record pointing to the server they are hosted on.

To see which server they are on see the site list spreadsheet.

• IPRO-WEB1 is 62.233.113.122
• IPRO-WEB2 is 62.233.113.123
• IPRO-WEB3 is 62.233.113.124
• IPRO-WEB4 is 62.233.113.125

SPF

A TXT record should be created containing an SPF record to reduce the chances of email being marked as spam.  If they already have an SPF it should be amended.  See the guide for more details

DMARC

A TXT record should be created containing the DMARC record for the domain.  This should only be set up of there is a valid SPF record in place and if their existing email system also signs their emails with DKIM.  Ideally a custom DKIM record should be added for SocketLabs as well, although if this isn't present the default SocketLabs key will be used instead.  To add a DMARC record create a TXT record with name _dmarc and value ""v=DMARC1; p=none;".

This can be tested by querying the DNS for _DMARC.example.com.

Socket Labs

If they are using socketlabs then a number of records need to be created.

• A MX record called inbound.example.com that points to mx.socketlabs.com
• A CNAME record called bounces.example.com that points to tracking.socketlabs.com.  Add the entry to the Custom Bounce Domain page in SocketLabs.  This will customise the host name used in the return address and message ID.
• A CNAME record called email.example.com that points to tracking.socketlabs.com.  Add the entry to the Engagement Tracking Settings page in SocketLabs.  This will customise the URL used for click tracking in emails.