Network Configuration for Ticketure eCommerce Site

DNS Site Name Resolution

For eCommerce, Ticketure leverages DNS delegation for the subdomain that a customer is using. Meaning that for a subdomain of ‘tickets’, the customer will leverage NS (NameServer) entries to delegate the answer of ‘tickets’ to the Ticketure.com domain. This will only impact the ‘tickets’ subdomain and enable SSL management, failover, and environment management without the involvement of the customer.

The configuration will vary based on the Data Center in which your Ticketure Instance will be located. For instances hosted in the North America Data Center - please follow the North America Data Center instructions. For those hosted in the European Data Center, please follow the European Data Center settings.

North America Data Center

NS Settings

Customers need to define the following NS entries for the subdomain that Ticketure will manage.

DKIM Settings (CNAME and SPF)

Customers need to apply the following CNAME entries for DKIM resolution

where <domain.com|org> in the entry is the root domain of the customer site and <slug> in the text portion is the tenant slug/prefix from Ticketure.

Example: 

For an organization with myorganization.com as their domain with a Ticketure slug or prefix of myorg:

In addition, appending the following to the customer’s existing SPF record

European Data Center

NS Settings

Customers need to define the following NS entries for the subdomain that Ticketure will manage.

DKIM Settings (CNAME and SPF)

Customers need to apply the following CNAME entries for DKIM resolution

where <domain.com|org> in the entry is the root domain of the customer site and <slug> in the text portion is the tenant slug/prefix from Ticketure.

Example: 

For an organization with myorganization.com as their domain with a Ticketure slug or prefix of myorg:

In addition, appending the following to the customer’s existing SPF record