mx records
Hi, I configured my ns records from my domain to cloudflares but where can i configure the mx records from my mail its disabled on my domain provider because i changed my ns records but now i cant receive any emails in my mailbox from my provider. My provider is strato.
30 Replies
I mean simply configuring strato mail to cloudflare
You would add the MX Records you need for Strato/had at your old dns provider in Cloudflare, under DNS Records : https://dash.cloudflare.com/?to=/:account/:zone/dns/records
I dont have stratos mx records
How did it work on your previous registrar then?
Strato had auto done the mx records and txt with their own but i dont got them
Here's a previous forum thread from January, regarding a Strato set up: https://community.cloudflare.com/t/not-able-to-recieve-mails-trough-cloudflare/455069
Shortcut - MX: https://community.cloudflare.com/t/not-able-to-recieve-mails-trough-cloudflare/455069/7
Shortcut - Domain authentication, TXT (SPF) record, et cetera:
https://community.cloudflare.com/t/not-able-to-recieve-mails-trough-cloudflare/455069/10
So the smtp.domain.com and pop3, imap also work
And with the txt there are 3 different mx records and 2 txt so where do i need to put then
Them
Got 530 5.7.0 User not authenticated
There should only be one MX record on the above link (the one marked as solution)? 🤔
Did this one come while trying to send a message?
If so, it would typically be one of the following reasons:
#1: You're either not connecting to the right server for outbound mails (which may not be the same as the one in your MX record).
#2: You've forgot to tell your email client to authenticate with the outbound mail server, using your username (often just your email) and password.
Can you explain the second more
If #2 is the culprit, your email client (e.g. Thunderbird) literally needs to authenticate, e.g. to say "Hi, I'm
[email protected] with the password ch4ng3m3", before it is trying to send the message.
If it doesn't try to authenticate (e.g. log in) before sending an message, a such error like the "User not authenticated" may appear.
How you can set up your email client to do that, depends on which email client you use, for Thunderbird, there is an example here:
https://www.hostpapa.com/knowledgebase/set-smtp-authentication/
In the example with Thunderbird, that link was one of the results found by Googling "thunderbird enable smtp authentication" (you can simply replace Thunderbird with the name of your email client, if you use something other than Thunderbird).I dont know if it could help here is my are my mx/txt records
But im sending from my mail to my strato email
My mail is a gmail from gmail
You haven't yet set it up / re-configured the MX records according to the link I've shared above.
1. Kill the MX with pointing to Mail server
smtp.strato.com.
2. Replace Mail server smtp.strato.de with Mail server smtp.rzone.de in the other (remaining) record.
Final result:
One single MX record, that according to your screenshot, would say:
smtp.rzone.de handles mail for {domain}.Should this also fix the problem that i cant send emails from the strato webmail site from the strato mail
The above will only change which mail server that third party mail servers (e.g. from outside Strato, Google's in case of Gmail) will connect to, while trying to send messages to you.
For problems regarding sending messages through Strato webmail, you would need to contact Strato.
Got outgoing mails working but ingoing still not
I gave you
smtp.rzone.de, ending with the TLD for Germany, .DE, NOT .COM.Though there wasnt a difference
You unfortunately cannot just assume such :/
And ... you aren't even guaranteed that Strato is the owner of
rzone.com, just because they got rzone.de, - so chances are, by assuming such, that someone else could possibly get their hands on your mails in this specific example.My problem sorry
Does cloudflare also take 24 hours for dns changes
It can take a long while, but that isn't necessarily Cloudflare (or whatever provider you use)'s fault.
If I am guessing right on your actual domain name, it appears you have the MX record set to Auto in TTL, which is 300 seconds (5 minutes).
So things could start to be functional from after 5 minutes has passed away.
However, your ISP's resolver could be also be deciding to cache the DNS for much longer, saying "5 minutes is too low TTL, we'll do a minimum of 14400 seconds (4 hours)", or even weeks/months, if they wanted to.
Ok
Using strato it is 24 hours
It is also a better choice than 5 minutes, if you ask me.
Assuming you're browsing around on your own website for 24 hours straight, with a TTL of 300 seconds (5 minutes), you would literally end up on being sending at least 288 DNS queries per day. Those 288 DNS queries could be limited to just one single DNS query, if the TTL was 86400 seconds (24 hours).
Some slow DNS (or bad connectivity between e.g. your DNS resolver and the authoritative DNS (Cloudflare in this situation) could also slow down your website a lot.
With a TTL of 86400 (24 hours), assuming your ISP would honour the TTL and keep the DNS entry in it's cache for that long, ... could therefore have the benefit of speeding up your website.
But it would at the same time have the unfortunate consequence that changing from old servers to new servers could be "slow", unless you plan in advance...
But, how often are you changing your servers anyway? 🙂
Pros/cons with everything 😉
Ok
?
Everything is working thanks for helping i dont understand anything of email records still but that doesnt matter because it works
Or the 24 hour change is only by changing name server dns records
Glad I could help 🙂
If you imagine DNS and it's TTL (Time To Live) is quite simialr to e.g. when you with your website tells browsers (or caches in between, such as e.g. CDN's) to cache your content for a while, so that your own server won't be bothered with the traffic, and the data will (temporarily) be available closer to your users.
If the 
) records in your Cloudflare, and things has been successfully for a while - you're already good to go.
Changing Proxied ) records from one IP adress to another will generally be near-instantaneous, as it is only an internal change within Cloudflare in that situation, where the IP addresses the public (e.g. you and I) see, will remain the same.
https://static.example.com/example.png image is cached by Cloudflare, often in in your own city (the datacenter you hit), the traffic will be very speedy.
You -> Cloudflare -> (you have the image)
If not, it will go:
You -> Cloudflare -> The server behind
If you have set some browser cache to cache the image for a year, you might have problems that you cannot change the image on the URL address above, since the browsers can remember the image.
DNS simply works the same way:
You -> Your router -> Your ISP's resolver -> The domain (e.g. example.com)'s name servers (for example Cloudflare).
However, if your router has it cached, it only goes:
You -> Your router
If your ISP has the DNS response cached already, but your router doesn't, you might go:
You -> Your router -> Your ISP's resolver
Since your router at least, but often also your ISP's resolver are very close to you, it will be very speedy this way due to the "DNS cache".
However, the DNS cache will similar to the web cache above cause issues, if you want to update the DNS, you might have to wait a while.
As such, there are pros/good things (very speedy) and cons/bad things (slow to update) with e.g. caches - no matter if it is web traffic or DNS traffic we're dealing with.
For changing name servers, I generally say expect to wait at least 48 - 96 hours.
.COM/.NET TLD's have a TTL of 48 hours with the TTL from the name server delegation.
Other TTL's vary a lot around 24-48 hours as well, but also some other are as low as e.g. 1-2 hours with the delegation TTL.
Sweet spot I've seen in real examples, for changing name servers .COM/.NET domains with the 48 hour TTL, is around 60 hours - until no problems are registered / reported any more.
Since the resolvers out there can make their own policies and overruling stuff to their own satisfaction - you generally wouldn't be able to give a 100% perfect / guaranteed "wait X (minutes|hours|days)" time for DNS propagation.
That said, -
If you're running with Proxied ) records in your Cloudflare, and things has been successfully for a while - you're already good to go.
Changing Proxied ) records from one IP adress to another will generally be near-instantaneous, as it is only an internal change within Cloudflare in that situation, where the IP addresses the public (e.g. you and I) see, will remain the same.I have a .com
If you ever need to change the name servers of the domain again, - I would expect 48-96 hours with potential problems starting from the successful change.
^ Always remember this specific one
And otherwise, you often don't need to worry unless you see something indicating there might be issues 🙂
Ik