https://treepl.co/public-backlog-state/request/multiple-domain-names
Am I missing something? Is this not a feature duplicated by the DNS? How would this be different that creating a CNAME record on your DNS for a subdomain, or a CNAME record to forward a second domain to a landing page on the first?
(Frankly, I’m just curious how this item has so many votes in the backlog?)
You can’t forward a domain to a specific landing page using DNS (or can you?).
It’s also much more convenient to manage these aspects of all the site domains in one place as it’s often challenging to get access to DNS settings if the domain is managed by the client or a 3rd party.
I’m no expert in this area, but I also think some DNS settings for controlling how a domain redirects/forwards, etc. can conflict with those needing to be set up on the server side - so there could be issues in that regard too perhaps.
We had these types of controls in BC’s domain manager and I thought that was a good way of doing it and the client could change landing pages if needed - without risking major damage by playing around with DNS settings.
I’m also no expert in this area.
I’ve never tried to used a CNAME record to forward a url to a page, but you can forward a domain to a directory. I did some quick research and it seems like it’s not impossible to forward to a page.
@alex.n Can DNS setting that would point a domain to a directory with a CNAME record cause issues?
These types of controls in BC’s domain manager were DNS settings (or was there another way of doing this?). So really what we’re asking for here is for treepl to build a DNS for us and integrate it into the admin panel. @alex Is this on the roadmap?
I mean it makes sense if we’re going for a 1:1 match to BC features.
You can’t really point domain to a directory, if we’re talking about pure DNS functionality.
CNAME can only point to another domain name and domain name (A or AAAA) points to an IP address. If DNS provider lets you point domain to a folder, it means that request first goes through their web server, gets rewritten and redirected to an actual domain address. While possible, it’s not very common.
And the problem with it is fragmentation, where neither DNS nor CMS are aware of each other and you have to make sure that both are synchronized.
Whereas if redirects happen on CMS server side, everything is managed in one place, domains and folders can be linked transparently, etc.
That’s just my quick opinion on overall approach to domain redirects.
Thanks @alex.n for your response. It sounds like this is a needed functionality this is not duplicated by the DNS for people who need domains to go to distinct landing pages.