Share
Explore

Domain Masking

Zuddl lets you add a custom subdomain for your event sites like "events.acme.com" or "conferences.acme.com. The subdomain (“events” or “conferences” in the above example), once mapped to your organization in Zuddl, can be used to host all your events instead of app.zuddl.com.
Adding a custom subdomain
The subdomain for events is mapped to your organization in Zuddl. There can only be one subdomain for each organization.
Important
The entire process of mapping and validating a new subdomain to your organization in Zuddl may take up to 5-7 days. Ensure that you take into account this time frame before organizing your next event.
Prerequisites
Decide on a suitable subdomain name such as events.acme.com or conferences.acme.com that can be used for all future events.
Send an email to your account executive or the CSM at Zuddl with the following details:
Organization name
Name of the subdomain
Upon receiving your details, Zuddl maps the given subdomain to your organization in the backend. Once the mapping is successful, a confirmation email is sent which contains two CNAME records: a subdomain name and a random unique validation string. The following sections describe them in detail.
Steps to add your custom domain
Once you’ve received the confirmation email:
Sign in to your domain host.
Tip: If you don’t know your domain host, check your billing records in your mailbox or visit
In your domain's DNS records, create two CNAME records:
The subdomain name that points to your domain. For example, if you want to represent virtual.foobar.com, enter “virtual” in the Name column. In the corresponding Value column, copy and paste the value shared in the confirmation email.
A unique string for verifying the ownership of the subdomain. For example, _c3e2d7eaf1e656b73f46cd6980fdc0e. This unique string points to the ACM validation certificate which is the validation server. For example, _cjhwou20vhu2exampleuw20vuyb2ovb9.j9s73ucn9vy.acm-validations.aws
A validated ACM generates an SSL/TLS certificate for your subdomain.
DNS Records
0
S.No.
Name
Record type
Value
S.No.
Name
Record type
Value
1
1
examplestring.virtual
CNAME
randomstring.acm-validations.aws
2
2
virtual
CNAME
foobar.randomstring.cloudfront.net
There are no rows in this table
Once the records are added to your DNS, the validation may take up to 48 hours. After successful validation, the events can be hosted from the new custom subdomain instead of app.zuddl.com
Warning
0
Note
Note
1
The CNAME records sent by Zuddl must be added to your DNS within a prescribed time window of 48 hours to avoid the expiration of the records. Should the records expire, the same process needs to be followed to make a fresh request.
There are no rows in this table
Important:
The event setup side remains unaffected by the domain changes for the live site and can only be accessed from app.zuddl.com.
The subdomains mapped are at the organization level. Any event created by the organization is mapped to the custom domain set.
Future changes to the custom domain follow the same process as explained above.

Use of root domains
For adding a custom domain, we only accept subdomains (www.acme.com) and not root domains (acme.com). This is because, unlike root domains, sub-domains don’t need a static IP address and they allow CNAME records for mapping with a custom domain. As a workaround, you can configure a redirect in your DNS for your root domain (for example, acme.com) to a subdomain of your choice (www.acme.com), and we can map the custom domain with the subdomain.


Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.