I've got a domain myawsdomain.com on AWS through Route 53.
I have an email server set up with a different service under a different domain myemaildomain.com.
I have an email account set up for fred#myemaildomain.com.
I'd like to have an address inquiry#myawsdomain.com forward directly to fred#myemaildomain.com. Is there a way to do that with just DNS, or am I going to need an email server running at myawsdomain.com to make this happen?
You can point the MX records at any provider willing (and configured) to handle email for your domain. Most paid email hosts will allow you to point multiple domains at their service.
MX records are separate from your other records, so you can point your A at AWS and your MX at, say, Google Apps. (Note: there are special oddities with CNAMEs - they can't coexist with a MX.)
Related
I am using Google Cloud for running a website, accessible on mydomain.com (fake, for illustration). I am trying to figure out how to receive email at support#mydomain.com (and let it be accessible by a human like a normal email) and also be able to send custom emails from info#mydomain.com programmatically. I am not sure what technology I am missing to be able to do this.
I have a k8s cluster with an Ingress with a static IP exposed through Cloud DNS zone. The NS records for mydomain.com. match the NS records on Google Domains. This works and I can access my website as expected.
From a little bit of research, I think I need to use something like Sendinblue because using their service will likely make my emails more legitimate. I purchased a dedicated IP in Sendinblue. Following this guide, I added ns1.sendinblue.com and ns2.sendinblue.com NS records for mail.mydomain.com in my Cloud DNS zone. I have associated the domain in Sendinblue and picked matching NS records. Then I created a sender and I am trying to verify this sender, but I have no inbox. This is the most confusing part. So I found this question-answer and followed by adding MX records and setting up email forwarding to mydomain+support#gmail.com (a plain Gmail account).
So now I expect any emails sent to support#mydomain.com to be accessible from the plain Gmail account. When I send emails, I do not receive them but I also do not get back a delivery failure. I've waited 12+ hours to make there isn't a DNS delay.
I feel like I haven't wired up these pieces correctly together and I am missing something but I am not sure what.
This is the answer publish by John Hanley added as community wiki since #John Hanley did not add as answer:
"
Select a normal mail service (Google Workplace, Office 365, Zoho (which offers a free account) and set up mail on your primary domain. Use Sendinblue as your email marketing tool - as it is not a general purchase email system
"
I am quite new to webadmin (esp email setups), and I am in the process of setting up emails for an app (mydomain.com) which is hosted elsewhere (a VPS provider via cloudflare dns)
I have a small shared hosting plan with directadmin acces with another provider, and I am wondering as to how I set up an email only system for my app (which is hosted elsewhere), with this shared hosting provider.
My questions are:
[1] Do I simply point the MX record for the domain (in cloudflare) to the shared hosting IP address and create the email addresses with directadmin?
[2] Do I need to add my domain name in directadmin? or do I add mail.mydomain.com?
Any help or pointers to this will be great!
For the first question, Yes. You need to point the MX Record to the shared hosting IP and create the email adres in directadmin
[2] If you want to use you domain for the email then you need to add the domain indeed. After that you can add custom email prefixes (info#example.com) to that domain.
For more information about this you can always read:
http://www.site-helper.com/
I am trying to get my mail exchanger record to point to sendgrid, but I cannot seem to find the option on heroku. Does anyone know where this setting is located?
Unfortunately, as far as I can tell, Heroku does not allow you to set MX records for their subdomains.
To counteract this, you can do one of two things. You may setup MX records for some domain (or subdomain) you own, and point that to SendGrid. OR you may use the preconfigured bymail.in. This service has MX records preconfigured to send to SendGrid. To use it simply direct your users to email your-sendgrid-or-heroku-username.bymail.in (e.g. yay#nquinlan.bymail.in).
My client has their domain name (lorem.com) registered with company X which also host their email. I'd like to host their new website with separate hosting company (company Y). I know I need to update the DNS nameservers for their domain name to point to company Y's nameservers. I'm not sure how to handle the email host though. Doing an MX lookup on their domain, currently shows:
Pref Hostname
10 lorem.com
20 mx2.companyX.com
Do I need to do any updates to the MX record? Also, do I need to add/edit the A record to point to company Y's IP address? Thanks!
So if I understand correctly, you are migrating only your website from the old hosting company to a new hosting company.
Do I need to do any updates to the MX record?
No, since you want the old server(hosting company) to keep managing your emails, no changes to MX records are required.
Also, do I need to add/edit the A record to point to company Y's IP address?
Correct. All you need is to put in a new A record to company Y's IP. Remember to change the A record for .(root) and www (if www subdomain exists) and any other sub-domains that your website may have (eg. ftp etc.)
I have a registered domain name where the emails are handled by windows live admin center having a single mx record for my domain. I also have access to modify the dns records any time.
We have around 20 email registered in windows live for my domain. for e.g. user1#example.com, user2#example.com etc.
Some users want to go in for google app accounts as they say there are lots of features in it, and therefore I think I need more than one mail server in my organization.
Is it possible that i can have some emails redirected to windows live and some to google apps, provided that I have access to change the dns and mx records?
So you want different users for the same domain to go to different mail servers?
You can't do this by manipulating the DNS records - the mail will be delivered to the server(s) defined by your MX record for the domain without any reference to the user name.
However, there's nothing stopping that mail server being an application that forwards mail onto several other servers based on the user name of the recipient...
This can't be done within the DNS - mail routing is done on the domain part only.
You'll need to arrange for all of the mail to arrive at one central place, and for it to be then forwarded-on depending on who it's for.
Do note that that isn't completely trivial, although any decent mail server should be able to do it. This is because in some cases (cc:, etc) that forwarding will need to result in two copies being forwarded, i.e. if there are multiple recipients and they're not all on the same service.