We are in the process of building a Multi-Tenant, SaaS type web app. Everything is set to go on the application part but when it comes to email there is a problem.
Each tenant/user of the application has a subdomain based account. However, there will be the option for that tenant to associate a top level domain to their account. Here is where the problem comes for us.
Basically, if the user sets up their DNS to point to our SaaS web app everything works good on the app front except that it now makes us responsible for handling their Email as well. Incoming and Outgoing.
What is the best way to handle this? I really was hoping their is a 3rd party site that handles outgoing and incoming email for multiple top level domains under one company name but am unsure.
There is always the option of doing our own SMTP/POP service, but we would really like to steer away from the responsibilities of email.
Thanks everyone,
~kvq
Can't they just setup an A record or a CNAME to point to your servers?
If they did an A record it would allow just webapp.theirdomain.com to go to your severs and everything else can just stay on their DNS.
The other option and maybe a better option is for them to setup a CNAME. Then you can just setup companyA.yourdomain.com and then they can just setup a CNAME that points webapp.theirdomain.com to companyA.yourdomain.com
You really do not want to be responsible for all of their DNS. They can keep their DNS where ever they want and keep their MX records the way they are.
I hope this helps
Related
I am building a Saas platform (lets assume domain is www.saas.com) where user have unique subdomains such as user1.saas.com, user2.saas.com etc. And give them a feature to add their own custom domain.
To add custom domain, users define cname for app.saas.com and A record for public id in of my app.
Everything is working fine if cname and A record is defined correctly by users. But i have two concers about this:
To host my app, i used cloudways and select digital ocean servers. But if i want to move from Digital Ocean to AWS at some point, then public ip is going to change. So custom domains wont work until users change their A record.I wonder if is there a better way to give custom domain feature to user instead of adding A record? (I am not sure if cname and a record is the correct way for this feature)
Let's assume user1 is defined own domain for user1.saas.com. When i go to user1.saas.com, it is also working. I think, i should redirect this url to custom domain if it is defined. I wonder if this is a correct way?
Thanks in advance
Anil
Firebase hosting requires that a TXT setting be set up to as they call it
Prove the domain is yours
I purchased a domain. It is mine. In order to set this TXT setting I have to have the domain hosted. The place I purchased the domain from sells hosting for minimum one year at a time. What is the point of firebase hosting when I have to buy hosting somewhere in order to prove that the domain is mine? Is there any way to get around this catch 22?
Proving ownership is done by putting a TXT record in the DNS. This doesn't require that you have a website hosted yet, it merely requires access to the DNS settings for your domain.
It's hard to help beyond that without knowing where you registered your domain.
Update. I took Frank's advice and set up a few Namecheap accounts. Wowie! The discount names are as cheap as 50 cents/year if you buy 1 or 5 years. Thanx for the advice. There is a caveat to using Namecheap/firebase, however.
Do not take this as if I were looking a gift horse in the mouth. I am super grateful to Google for free hosting. I merely want to warn users that firebase is not a free country. Google forces the s religion. I put in many hours of work to create my website using my girlfriend's hosting MySQL. Her hosting platform does not have an s in the URL: https. So the Angular 5 HTTP calls barf. I also included a contact page and a share via email popup. I used my girlfriend's hosting and set up a poor man's PHP web service for that. That does not work because girlfriend's hosting uses HTTP not https. So now I have to go back and recode these backend connections to use Google firebase and Google functions/SendGrid. I could have done that from the get-go and saved myself the time and aggravation.
I recently acquired a domain while buying a logo and some business cards through logomaker.com. I took this opportunity to claim the domain that I want to use for my rails app on heroku (Was this a mistake?).
Currently I seem to be required to use Weebly to edit the site for this new domain (But I'm thinking about transferring the domain to my GoDaddy account for simplicity. Is this a good idea?) I'm trying to route the simple domain to my rails app. In other words, I want users to be able to type mrzschool.com and get routed to mrzschool.herokuapp.com. I haven't been able to find a way to do this through Weebly.
I also have access to DNS and nameserver settings, such as imap and pop, through logomaker.com. This seems like it might be a way to change the routing, but I'm realizing that I'm unschooled in the realm of domains and DNS.
I'd suggest you go through the the process of moving your domain registrar from logomaker to your goDaddy account, were you can keep an eye on this domain along side any other domains you've there. It's a tedious process but worth it in my opinion. However, it's optional since you have all the control you need to do that via logomaker.
The heroku docs mentions (found here) how you can point your own custom domain to your heroku app subdomain. Keep in mind that you will need to verify your account and your ownership of the domain.
You will also find some useful troubleshooting steps here.
I bought domain names on AWS Route53.
I launched the websites on S2.
Now, I cannot setup new email addresses.
SES/EC2 are ready-to-go solutions.
I want to:
Create new email addresses ASAP (business trip in 10 days)
Simple daily-email, no newsletters, no mass emails
Ready-to-go solution, no installing/configuring of complex technical systems like Linux, Ubuntu, SquirrelMail, Google Apps systems...
I was referred by a MX record based system used by Outlook; unfortunately this service is no longer available.
Questions:
Is there any easy and simple solution using Route 53/SES/EC2 ?
Or, any 3rd party service that I can use ? (ideally, something free – I do not want to pay 50$/year per user)
There is a pretty straight-forward free service that I'm using called Zoho:
https://www.zoho.com/mail/
I'm new to it as well, so I can't speak to its reliability, but setup is pretty easy. It will have you verify your account by creating a record set in your 'Hosted Zone' page in Route 53.
for creating webmail there's a WorkMail option on aws services. you can create an email account there.
first click on add organization button . then go to quick setup. fill the requirements. after it's done click on the organization name that you already created and create a user.
enter a username and password that you want. after creating user , you can find the webmail url on "organization setting tab".
the WorkMail can integrates nicely with SES.
I work for a company which has its own web server they are due to have a complete power blackout over the weekend, meaning their servers will be down.
Does anyone know a way we could present a down status on a maintenance page or some kind of redirect so we can at least inform our users that the site is down for maintenance and not just missing/broken?
The best way is probably setting up a redirection to dummy server on your load balancer or border routers. If you have no such thing, then you can either try asking your provider about the options, or temporarily change the DNS record, provided that you reduce DNS cache timeouts before and after the change, so it takes effect immediately.
Set up a server on another location and point their domains DNS record to that server during the blackout.
The redirect has to be carried out by the web server. No web server, no redirect. What you can do is to get another web site by a web hosting company (which will not be subject to your blackout), and configure it to route requests from your main dns to the temp site with just a plain notice html page, then remove it once power is restored. This can be done if you have the dns info from the primary site. You could also mirror the site this way, and then shut down the mirror and no one will be the wiser. Try http://siteground.com I have used them for years.
If you are using a load balancer, see if it supports a "Sorry Server" page. Most of them have this feature built in.