Skip to content
  • There are no suggestions because the search field is empty.

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

There are 2 data centers in North America (east and west). You can determine which one you are on by checking your CMS domain (i.e ticketure.com or ticketure.net). If you are on the .com instance, use ticketure.com in the records below. If you are on the .net instance, use ticketure.net in the records below.

NS Settings

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

  • ticketure.com
    • ns1.ticketure.com 
    • ns2.ticketure.com 
    • ns3.ticketure.com 
  • ticketure.net
    • ns1.ticketure.net 
    • ns2.ticketure.net 
    • ns3.ticketure.net 

DKIM Settings (CNAME and SPF)

Customers need to apply the following CNAME entries for DKIM resolution for ticketure.com:

  • ticketure1._domainkey.<domain.com|org> 
    ticketure1.domainkey.<slug>.domains.ticketure.com
  • ticketure2._domainkey.<domain.com|org> 
    ticketure2.domainkey.<slug>.domains.ticketure.com
  • ticketure3._domainkey.<domain.com|org> 
    ticketure3.domainkey.<slug>.domains.ticketure.com

Customers need to apply the following CNAME entries for DKIM resolution for ticketure.net:

  • ticketure1._domainkey.<domain.com|org> 
    ticketure1.domainkey.<slug>.domains.ticketure.net
  • ticketure2._domainkey.<domain.com|org> 
    ticketure2.domainkey.<slug>.domains.ticketure.net
  • ticketure3._domainkey.<domain.com|org> 
    ticketure3.domainkey.<slug>.domains.ticketure.net

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.

For example, an organization with myorganization.com as their domain and a Ticketure slug of myorg on the ticketure.com instance should use:

  • ticketure1._domainkey.myorganization.com 
    ticketure1.domainkey.myorg.domains.ticketure.com
  • ticketure2._domainkey.myorganization.com 
    ticketure2.domainkey.myorg.domains.ticketure.com
  • ticketure3._domainkey.myorganization.com 
    ticketure3.domainkey.myorg.domains.ticketure.com

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

  • ticketure.com
    • include:spf.ticketure.com -all 

  • ticketure.net
    • include:spf.ticketure.net -all 

European Data Center

NS Settings

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

  • ns1.ticketure.co.uk
  • ns2.ticketure.co.uk
  • ns3.ticketure.co.uk

DKIM Settings (CNAME and SPF)

Customers need to apply the following CNAME entries for DKIM resolution:

  • ticketure1._domainkey.<domain.com|org> 
    ticketure1.domainkey.<slug>.domains.ticketure.co.uk
  • ticketure2._domainkey.<domain.com|org> 
    ticketure2.domainkey.<slug>.domains.ticketure.co.uk
  • ticketure3._domainkey.<domain.com|org> 
    ticketure3.domainkey.<slug>.domains.ticketure.co.uk

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.

For an organization with myorganization.com as their domain and a Ticketure slug of myorg

  • ticketure1._domainkey.myorganization.com ticketure1.domainkey.myorg.domains.ticketure.co.uk
  • ticketure2._domainkey.myorganization.com ticketure2.domainkey.myorg.domains.ticketure.co.uk
  • ticketure3._domainkey.myorganization.com ticketure3.domainkey.myorg.domains.ticketure.co.uk

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

  • include:spf.ticketure.co.uk -all