SaaS, Route 53, and WordPress DNS issues
-
Hello,
I’m having an issue that myself and a devops assist cannot resolve. Here is the scenario:
* I want the website, where content is hosted for regular vistors, to be hosted by WordPress
* I need my SaaS application to be a series of instances on AWS
* Customers need to be able to create subdomains (think customer.mywebsite.com)
* This means using Route53 on AWSThe CNAME / A records are hidden when I link a domain to my wordpress site. When I remove the link, and use Route53 to point to the address given as the website address I can use as an alternate primary (no custom domain), I get an error that I’ve not linked a custom domain to the site and so can’t do that.
How can I get around this issue? I don’t want to have to move my site off the service, but I can’t hold the SaaS app hostage to WordPress DNS either.
The blog I need help with is: (visible only to logged in users)
-
I know the site is showing as unreachable atm as DNS is propagating again back to the WordPress name servers. I really just want to use the domain I own, purchased elsewhere, for the WordPress site, without having to also use WordPress DNS.
-
Website is back after DNS propagation. Still need to figure out how to use Route53 as DNS while hosting my primary website content here.
-
Hi @timskalawp,
It sounds like you’re trying to do two separate things here — host a site on WordPress.com, while also setup a SaaS of some sort on AWS.
Since you’re not looking to use WordPress.com nameservers, I have emailed you A Records that you can use instead.
With regards to the other piece of the puzzle, you might want to consider a subdomain: https://wordpress.com/support/domains/connect-subdomain/
Hope that helps!
- The topic ‘SaaS, Route 53, and WordPress DNS issues’ is closed to new replies.
WordPress.com Forums 