I cannot get email forwarding from my godaddy domain to my gmail. When I send an email to the address, I get the email (from my gmail only) and a message saying address not found.
Setup is:
Godaddy domain and emailforwarding
Netlify to mangage the DNS (it's where the site it managed too)
SMTP2GO to manage email sending an configuration
In GoDaddy, the MX settings are active with the green tickmark showing.
In Netlify, I have input the MX records from GoDaddy.
In SMTP2GO, the SPF and DKIM records are verified.
What am I doing wrong?
Thanks
If netlify is managing DNS, then the MX records in Godaddy are ignored. You can tell this by using whois:
$ whois fools.website | grep -i "name server"
Name Server: DNS1.P05.NSONE.NET
Name Server: DNS2.P05.NSONE.NET
Name Server: DNS3.P05.NSONE.NET
Name Server: DNS4.P05.NSONE.NET
Netlify's nameservers all match the same pattern of DNSx.P0X.NSONE.NET
If your whois lookup returns similar results, you'll want to instead configure everything you have in your DNS settings in Godaddy at Netlify's DNS config, usually https://app.netlify.com/account/dns/domain.name (where you replace domain.name with your actual domain name like mynetlifysite.com)
If your whois records look more like this:
$ whois godaddysite.com | grep -i "name server"
Name Server: PDNS03.DOMAINCONTROL.COM
Name Server: PDNS04.DOMAINCONTROL.COM
Then you'd want to work with Godaddy's support on why the records aren't working as expected since they do host/manage your DNS.
Point Godaddy's DNS to Netlify. Then from Netlify, add MX record of SMTP2GO. Lastly, create alias from STMP2GO that points to your Gmail email address. In my case, I'm using Namecheap instead of Godaddy and ImprovMX instead of SMTP2GO. I posted this here
https://marvintan.com/posts/free-custom-email-address/
Related
I just purchased mail domain service to my new domain.
Domain was registered in GoDaddy, mail domain purchased also in goDaddy( looks like outlook365)
But Nameservers are routed to Google nameservers, because hosting is in Google Cloud
I already did all setup in Google DNS Cloud yesterday, but still unable to continue to complete email setup in GoDaddy portal.
Before we can finish setting up your account, we need to verify that you own domain>
Sorry, we can't verify your settings, yet. It can take up to 24 hours for us to detect the update. Please double-check you entered the information correctly, and try again in a bit.
Here are my screenshots from GCP DNS
So I am not sure if I did correctly all settings in Cloud DNS.
Can you plese check my conf in GCP DNS ?
Specially I am not sure if I've filled correctly SRV, TXT data fields,
So I receive this conf info from Godaddy : how to setup >
1)
TXT Record: Find where to add a TXT record and enter
Name TXT Value
# MS=ms5789897
# v=spf1 include:spf.protection.outlook.com -all
2)
CNAME Records: Find where to add a CNAME record and enter
Host Points to
autodiscover autodiscover.outlook.com
sip sipdir.online.lync.com
lyncdiscover webdir.online.lync.com
email email.secureserver.net
msoid clientconfig.microsoftonline-p.net
3)
MX Records: Find where to add an MX record and enter
Host Priority Target
# 0 mydomain.mail.protection.outlook.com
4)
SRV Records: Find where to add an SRV record and enter
Port Protocol Name Service Priority Weight Target
443 _tls # _sip 100 1 sipdir.online.lync.com
5061 _tcp # _sipfederationtls 100 1 sipfed.online.lync.com
Ok, finally mail setup is done. :)
Issue was TXT verification, I got multiple TXT records in DNS before...FIxed, so feel free to remove this topic :)
I have a domain name, mysite.com registered with a provider at ns1.dnsprovider.com and ns2.dnsprovider.com.
mysite.com is a Wordpress site on WHM/cPanel at IP: 111.222.333.444
I can set my DNS records at DNSProvider to point at 111.222.333.444 for the websites - no problem. I also need to set up email facilities.
This I'm struggling with. I'm simply running the standard Exim package in cPanel.
I figure I need to set up an A record mail.mysite.com for IP 111.222.333.444 but I also need to set up MX records. Would this be to mail.mysite.com with priority 0 and 10?
Also what about DKIM and SPF records? What would I need to enter?
First a quick note: If the mail server is on the same IP address you do not need the extra A record, since there is already an A record the MX record can use.
As for the MX record, it depends on what the mail addresses will be. For the one you mentioned the mail addresses will be user#mail.example.com, if you want them to be user#example.com, then the MX record must be for example.com, like this:
# MX 10 mail.example.com.
Where mail.example.com is the extra A record you wanted to create, you can also point the record to example.com, since it has an A record pointed to the IP of the mail server.
Now for the SPF record it depends on which servers will be send mails on behalf of your domain. If only your server (this includes your web site, since they are on the same IP) the SPF record can be like this:
# TXT "v=spf1 a -all"
This allows the IP of your A record to send mails and "forbids" everybody else.
The DKIM record is in the following format:
default._domainkey TXT "v=DKIM1; p=yourPublicKey"
You should generate yourPublicKey and also a private key, with which you will sign your mails (note that you can simply skip the whole DKIM part)
Have searched everywhere, can't find answer.
I have the domain mydomain.com. The root and www records point to my main server, which runs my website.
I am now using a separate AWS ec2 instance to set up an email server for my domain. This is running on the subdomain mail.
My dns looks like this:
A # webserverip
A www webserverip
A mail ec2ip
To prevent my server from getting flagged for spam, I submitted the amazon reverse dns form here: https://aws.amazon.com/forms/ec2-email-limit-rdns-request
I gave them the ip of my ec2 mail server, and put "mail.mydomain.com" in the "Reverse DNS Record for EIP 1" box.
However, I keep receiving emails back from them saying:
When attempting to map the reverse DNS entry, we notice that this is failing because the PTR record doesn't match the A record for that domain.
We currently require the forward A record to match the PTR record for all reverse DNS entries.
I really don't understand what I am doing wrong. The "mail" subdomain has an A record pointing to my ec2 server ip. Any assistance would be greatly appreciated!
(I am using cloudflare for my dns if this makes any difference)
You can follow these steps to configure the DNS for your EC2 dedicated mail server on AWS:
STEPS
Add two A host records for pop.mydomain.com and
smtp.mydomain.com that point to your elastic IP and assign your
MX record to the smtp.mydomain.com host.
Add a CNAME record (not A host record) for mail.mydomain.com that points to the DNS entry assigned by AWS (e.g., ec2-XXX-XXX-XXX-XXX.REGION.compute.amazonaws.com).
Submit your rDNS request for smtp.mydomain.com mapping to your EIP.
Don't forget to add the SPF TXT record for your mail server. For example, v=spf1 mx a
Once you're done with this setup, you should have a proper mail server configuration in terms of DNS that would pass SMTP tests and avoids being flagged as spam.
We send out mail via Microsoft Exchange 2010 running on a Windows Server set up as server.organization.local.
When error messages are generated it shows:
Generating server: server.organization.local
I am confused as to what our SPF records should look like based on this. Should it simply contain the external IP address that this server uses to send out mail, or both this .local address and external IP address?
Currently it is set as:
# 10800 IN SPF "v=spf1 mx a:server.organization.local ip4:10.10.10.10 -all"
The mx is included to be safe but I'm not sure if it needs to be? The MX records on the domain name is set to a third-party filtering service, no mail is sent via it.
You need to specify the public IPs if you want to send emails to the internet.
If you are sending emails to another mail server on the LAN then you might have to add the private IPs as well.
I suggest to use a testing utility to check your SPF records.
I would like to set up SPF for my domain example.com on my own server but I don't really understand how to do this, so here are my questions:
1) What does my SPF record(s) have to look like if I would like to allow my server IP x.x.x.x sending mail using mail#example.com (or better *#example.com)?
2) Where do I have to add the SPF record? To my DNS records? How do I store it there???
3) I would also like to send Mails from my laptop using myname#example.com, and I'm using my server IP x.x.x.x as SMTP server, I guess that's not a problem with the SPF record then?
Hope it doesn't sound too stupid, but I find this SPF thing a bit confusing ;)
Use a SPF generation wizard, like this one: http://spfwizard.com/
1) What does my SPF record(s) have to look like if I would like to
allow my server IP x.x.x.x sending mail using mail#example.com (or
better *#example.com)?
In BIND record format, it could be something like:
example.com. IN TXT "v=spf1 mx ip4:x.x.x.x ~all"
Basically, it allows to send emails from:
all the MX records for example.com
the ip x.x.x.x
the other cases are qualified as softfail.
2) Where do I have to add the SPF record? To my DNS records? How do I
store it there???
You must be allowed to edit the DNS records for the domain example.com. Most likely it's a service provided by your registrar. You say you have 2 fields: you should add example.com (your domain) in the host field, and the "v=spf1.." string (withoud quotes) in the rule field.
3) I would also like to send Mails from my laptop using
myname#example.com, and I'm using my server IP x.x.x.x as SMTP server,
I guess that's not a problem with the SPF record then?
Well said, you got the point.