Avatar of IT Guy
IT Guy
Flag for United States of America asked on

Correct TTL value for domain MX record

What is the correct Time to Live (TTL) value that an email domain's MX record should be set to?
ExchangeMicrosoft 365Email ServersDNSTCP/IP

Avatar of undefined
Last Comment
footech

8/22/2022 - Mon
Dan Dhillon

Hi knowledgeable,

Should be 60 mins.
IT Guy

ASKER
Is 60 minutes the recommended setting for an Office 365 domain?

What happens if it is set higher?

The organization I am currently working for has it set to 24 hours. Will that present a problem or a security risk?
Dan Dhillon

In you office 365 admin centre you can run the domain verification tool which will tell you what ttl to use for mx records.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
IT Guy

ASKER
The organization I am currently working for has their email domain MX record set to 24 hours. Will that present a problem or a security risk?
ASKER CERTIFIED SOLUTION
Dan Dhillon

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
DP230

We often set it as 3600 seconds ~ 1 hour
footech

Frankly, there isn't any "correct" setting.  Whatever setting doesn't impact security at all.  A shorter TTL will result in more DNS queries, but has the advantage that if any change to the record is made, clients will generally be aware of the change sooner.  A longer TTL has the advantage that if the authoritative DNS server for the record is unavailable for a while, fewer clients will generally be impacted.

I say "generally" above, because whether it's a short TTL or long TTL, for a specific client, how long the record has left in the cache before a new query is sent depends on when the last query was the resulted in the record being cached.  In other words, even though a record may have a TTL of 24 hours, at a given time it may have only a few seconds before that time is up and it will have to query the DNS servers again.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.