Introduction
With eventpage.ai, you can run your community, event calendar, or event page on your own domain or subdomain.
Typical examples:
app.yourdomain.com
events.yourdomain.com
community.yourdomain.com
To make this work, eventpage.ai provides you with the required load balancer IP address. You then need to add this IP address as a DNS entry at your domain provider.
This guide will show you:
✅ Which DNS entry you need to create
✅ Where to add it at your domain provider
✅ What to expect after saving
✅ How SSL and verification work
What you need before you start
Before connecting your domain, make sure you have:
Access to your domain provider / DNS provider
The load balancer IP provided by eventpage.ai
The exact domain or subdomain you want to use
e.g. app.yourdomain.com
Typical domain providers include:
GoDaddy
IONOS
united-domains
Cloudflare
Strato
Squarespace Domains
Step-by-step guide / How it works
Step 1: Decide which domain you want to use
Choose whether you want to connect:
A subdomain
e.g. app.yourdomain.com, events.yourdomain.com, community.yourdomain.com
or
A main domain
e.g. yourdomain.com
⚠️ In most cases, using a subdomain is recommended.
💡 Tip: A subdomain is easier to manage and does not affect your main website setup.
Step 2: Get the load balancer IP from eventpage.ai
eventpage.ai will provide you with the correct load balancer IP address for your setup.
Example:
123.123.123.123
⚠️ Important: Always use the exact IP provided by eventpage.ai. Do not use old or guessed IPs.
Step 3: Log in to your domain provider
Open the admin area of your domain provider.
Go to the DNS settings or DNS records section.
Select the domain you want to edit.
Look for menu items such as:
DNS
DNS management
Zone file
Domain settings
Advanced DNS
📌 [Screenshot: DNS settings at provider]
Step 4: Create an A record
Add a new A record for the domain or subdomain you want to connect.
Typical setup for a subdomain:
Type: A
Host / Name: app
Value / Points to / Target: [Load balancer IP from eventpage.ai]
TTL: Default or 1 hour
Example:
Domain: yourdomain.com
Subdomain: app.yourdomain.com
DNS record:
Type: A
Host: app
Value: 123.123.123.123
💡 Tip: If you want to use events.yourdomain.com, the host would be events.
Step 5: Save the DNS record
Save the new A record.
Wait for DNS propagation.
DNS changes usually take:
A few minutes in many cases
Up to 24–48 hours in some cases
⚠️ Note: During propagation, your domain may not work immediately.
Step 6: Add the domain in eventpage.ai
After saving the DNS record:
Go to your Profile Settings in eventpage.ai
Open Domain & Sender
Add your custom domain or subdomain
Save the settings
eventpage.ai will then validate the setup and connect your domain.
SSL certificate handling
eventpage.ai manages the SSL certificate for your connected domain or subdomain.
This means:
✅ No manual SSL setup is required
✅ No separate certificate purchase is needed
✅ HTTPS will be enabled automatically once the domain is connected correctly
⚠️ Important: SSL can only be issued once the DNS record points correctly to the eventpage.ai load balancer IP.
Best practices & pro tips
✅ Use a subdomain like app.yourdomain.com instead of your root domain
✅ Double-check the IP address before saving
✅ Remove old conflicting A or CNAME records for the same host
✅ Wait for propagation before testing repeatedly
✅ Coordinate with your IT team if your company manages DNS centrally
Troubleshooting & FAQs
Q: Which DNS record do I need?
A: In most cases, you need an A record pointing to the load balancer IP provided by eventpage.ai.
Q: Can I use my root domain instead of a subdomain?
A: In some cases yes, but a subdomain is usually recommended because it is easier to manage.
Q: Do I need to configure SSL myself?
A: No. eventpage.ai handles SSL certificate provisioning for connected domains.
Q: My domain does not work yet. What should I do?
A: Check that the A record is correct and wait for DNS propagation. This can take up to 48 hours.
Q: Can I use Cloudflare?
A: Yes, but make sure the DNS entry is configured correctly. In some setups, proxy settings may need to be adjusted.
Q: What happens if there is already an A or CNAME record for this subdomain?
A: You need to remove or replace conflicting records for the same host.
