Growing ANAME / ALIAS support

# The problem with apex domains

You want to route your apex domain (also called bare or naked domain) like example.com directly to your app, and the hosting provider hands out a host name like myapp.example-host.com as the target. With standard DNS you cannot use CNAME records at apex domain level.

• CNAME records would solve the routing but break email delivery
• A records require IP addresses, which don't work with dynamic hosting services
• Email MX records cannot coexist with CNAME records at the apex

Read the apex domains article for more technical details and to understand whether you need apex domain routing.

# The (non-standard) solution

Different providers use different names for essentially the same functionality:

• ANAME (Address Name)
• ALIAS
• CNAME flattening

But they all work the same:

1. Acting like CNAME records - They resolve to the target hostname
2. Working at the apex - Unlike CNAME, they can be used for bare domains
3. Preserving email - They don't interfere with MX records

# Apex record support per DNS provider

Checked against each provider's own docs on 2026-10-13. "Any hostname" means the docs say the record can point at a host outside the provider's own services.

GoDaddy, IONOS, and DigitalOcean do not document an apex alias record in their help pages.

# Setting up ANAME/ALIAS records

The exact process varies by provider, but generally involves:

1. Log into your DNS management panel
2. Create a new record at the apex domain (@ or blank)
3. Select ANAME/ALIAS as the record type
4. Enter your target hostname (e.g., myapp.example-host.com)
5. Save the record and wait for DNS propagation

# What to do if your provider doesn't support it

If your current DNS provider doesn't support ANAME/ALIAS records, you have several options:

1. Switch DNS providers - Move to one of the providers above
2. Add a third-party DNS - Keep your domain registered where it is, but use a different provider for DNS
3. Use www forwarding - Redirect example.com to www.example.com

# Our conclusion

Since most browsers omit the www prefix and users barely notice it, we recommend using a forwarding service instead of ANAME/ALIAS/CNAME flattening. We don't think the aesthetic reasons hold up, as outlined in the apex domains article. You don't lock yourself in. There are no SEO implications, even if you move from bare to www domain.

On fortrabbit, apex domains are not routed directly to an environment. The free www forwarding service redirects the apex domain to the www domain, deep links included.