When you create a custom ticketing site, a unique
slug is generated for your site. By default, a Evvnt custom ticketing site is immediately available to be reached at its Evvnt domain.
By default, a Evvnt custom ticketing site is available at its Evvnt domain, which has the form
yourslug.evvnt.events. Your slug is created using the name you provide for your ticketing site. For example, a portal named
Bill and Ted would have the slug
bill-and-ted is hosted at
Note the slug name must be unique. If it is not unique, a unique token will be added to the end of it.
To make your ticketing site available at a non-Evvnt domain (for example,
tickets.yourcustomdomain.com), you add a custom domain to it.
Evvnt does not provide a domain registration service (for registering a customer domain name) or a DNS provider service (for hosting the DNS servers that point your customer domain name to your ticketing site).
Summary of steps
The remainder of this article covers these steps in greater detail:
- Confirm that you own the custom domain name. You can buy a custom domain name with a domain registration service.
- Provide your Evvnt account representative with the custom domain to add to your ticketing-site, they will provide you with two CNAME records to add to your custom domain.
- Configure your DNS provider to point to the Evvnt-supplied DNS target.
- Confirm that your site is accessible via the custom domain. There might be a delay while DNS changes propagate.
Configuring DNS for subdomains
After your account rep adds your domain, you need to point your DNS provider at the DNS target provided by Evvnt. They will provide you two CNAME records.
You usually configure two new
CNAME records. The first
CNAME points the subdomain at Geotix. The second one validates that you own the domain and is used to provision and auto-renew the SSL certifcate on that domain as long as that record exists. You can revoke permission at any time by removing the record.
. on the target domain may or may not be required, depending on your DNS provider. .
Consult your DNS provider’s documentation for specific instructions on creating
You can confirm that your DNS is configured correctly with the
host command, assuming your DNS changes have propagated:
$ host tickets.example.com tickets.example.com is an alias for yourslug.evvnt.events. ...
DNS changes can take between several minutes and several days to take effect. Lowering your DNS TTL ahead of time can minimize, but not eliminate, this propagation time.
Configuring DNS for apex domains
After your account rep adds your domain, you need to point your DNS provider at the DNS target provided by Evvnt. They will provide you with a CNAME record.
You will also need to add two A records to your DNS pointing to the IP addresses shown below:
Domain name glossary
- Apex Domain or domain name: full name used to access an ticketing-site (in words, not with an IP address). For example,
- Subdomain: the
- Root domain (or naked, bare, or zone apex domain): the ‘yourcustomdomain.com’ in 'www.yourcustomdomain.com’
- Wildcard domain: domains that match any subdomain, represented as
- Domain registration service: company that lets your buy and register a custom domain name
- DNS provider: company that maintains the DNS servers that translate a custom domain name to a destination ('DNS Target’). The fields are often called CNAME, ALIAS, ANAME, or A records. Only the first three work with Evvnt custom ticketing sites, as A records require an IP address and Evvnt custom ticketing sites do not have stable inbound IP addresses.
- Evvnt Domain: Evvnt term for default domain given to each ticketing-site. Has the form
[name of ticketing-site].evvnt.events
- DNS target: Evvnt term for the Evvnt domain to give to a DNS provider (e.g., in a CNAME record) to be the destination for a custom domain name.