Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know it could be very different based on the situation, but for hosting a website with no plans to move the hosting server what is a good TTL to set on the DNS record?

share|improve this question
up vote 13 down vote accepted

I tend to leave it at Slicehost's default, 86,400 seconds (1 day). I drop it down to 10 minutes when I have a move pending and wait a day or two.

share|improve this answer

1 Day is the recommended minimum default TTL as specified in RFC 1033.

RFC 1912 goes on to say that 1 day is probably too short and 3 days may be more appopriate.

share|improve this answer
I'd imagine DNS traffic from low TTLs was significantly more of a problem in 1987 and 1996 than in 2011/2012. – ceejayoz Nov 27 '12 at 22:33
Both those standards you quote are referring to the "Minimum" field of the SOA record only, which is no longer used for determining the default or minimum TTL anyway, as was intended back when those standards were written. DNS best practices written 27 and 18 years ago were written when DNS - indeed the internet - was a different beast. Nowadays, 300 seconds (5 minutes) is a fairly common TTL for main A/AAAA records, although only useful when needing fast failover otherwise 6 hours+ would be more appropriate. NS records, and the A/AAAA records for the NS addresses, are usually 1 day or more. – thomasrutter Jun 7 '14 at 16:02

I have noticed it is becoming more fashionable to have shorter TTLs to be able to respond in emergencies (particularly within HA DNS environments) quicker.

share|improve this answer

I'd just leave it at the default set by your host, unless it's ridiculously high or low for some reason. Then if you ever do want to move bump it down to 20 minutes or so a couple of days before you plan to do the move.

share|improve this answer

4 hours should be just fine, providing an acceptable balance. That's what I use on most zones.

share|improve this answer
That's probably way too short. – dmourati May 17 '11 at 0:19
@dmourati: It's 2011. For the overwhelmingly vast majority of small (i.e., under 1000 or so zones) DNS servers and for any and all clients the additional CPU load and bandwidth requirements are absolutely negligible. Of course, if your DNS servers go down for more than 4 hours you're SOL, but if that's important and you can't provide reliable DNS service you have no business hosting your DNS service on such a rickety foundation in the first place... – Mihai Limbăşan Jun 7 '11 at 17:48
When a user asks a question that is answered directly in an RFC you direct them to the RFC regardless of what year it is. – dmourati Jun 21 '11 at 3:17
@dmourati Is this prescribed in an RFC? – Joó Ádám Jan 3 at 4:38
Yes, see my answer above. – dmourati Jan 3 at 5:00

Besides RFC 1912, users in Europe should also see RIPE-203, "Recommendations for DNS SOA Values", which recommends two days as a minimum TTL value.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.