Does Galaxy support apex/naked domains? (

I really hate seeing www in front of a website. I just signed up for Galaxy and mLab and so far everything has been great, except it would appear an ugly www is being forced upon my app. :cry:

Would an A Record directed at ( work?


Ok, it looks like if I want an apex domain (aka naked domain), I’ll have to use a service that provides ALIAS. The Meteor Guide recommends dnsimple.

So far this is what I’ve got:

  • Galaxy for basic app hosting

  • mLab for database hosting

  • AWS for serving up images

  • MailGun for delivering emails

  • dnsimple for apex domain

Am I covered now?

I’m running on the exact same stack (minus AWS) and it’s been great for us. I can highly recommend DNSimple.


Very nice design. What do you use for image hosting (if applicable to your app)?

Very nice design.


The meteor app doesn’t have any images so no need for external hosting. Actually, you reminded me. We recently moved the marketing site to Zeit’s Now hosting and bumped the app onto an app subdomain. Marketing site images are simply hosted from Now.

If I was doing external image hosting I’d do it with S3 / CloudFront.

I’m guessing that using the naked domain is a strategic decision? If not, I’d strongly recommend checking out

Note that if you want naked domain redirection on galaxy, there isn’t a great solution at the moment. We are currently using

Interesting read. I had no idea not using www could lead to headaches down the line. I’ll have to reconsider my stance on this.

It may be silly but I simply don’t like the aesthetic look of www

However, if it will make things easier on my end, I’ll make the compromise. :slight_smile:

1 Like

I have everything working through an ALIAS record. Should I switch back to www or am I safe using an ALIAS?

// ******************* EDIT ******************* //

TL;DR: Using an ALIAS is perfectly fine and won’t lead to any issues down the line.

I found this helpful. Emphasis added by me.

What about ALIAS (or ANAME) records? – Augustin Riedinger Feb 27 '14 at 11:08

@AugustinRiedinger Those aren’t actually a DNS record type - they’re a configuration where certain DNS providers will handle the abstraction of dynamically checking the current A record of the target, then serving it back in response to a query for that name. They’re essentially designed to solve this exact problem, so they’re definitely appropriate to use for this case. – Shane Madden Feb 27 '14 at 17:31

So if we use them, the scalability warning from heroku doesn’t remain true anymore, right? Or is there any technical drawback into using them? – Augustin Riedinger Feb 27 '14 at 20:19

@AugustinRiedinger Correct. The technical drawback is in the implementation difficulty, as a “standard” DNS server cannot accomplish that kind of thing without customization. As long as your provider’s implementation is stable, it should be just as good as a CNAME setup on a subdomain. – Shane Madden Feb 28 '14 at 2:44

For anyone reading this thread, I highly recommend using DNSimple for this. They made Apex usage a non-issue.

1 Like