Dave Warren wrote:
Sure, but this adds undue load on my nameserver, and those of my customers for zones which I know will *never* change.
Ok, now I wee I misunderstood you, so never mind my comment about Dynamic DNS.
Now, what do you mean by load on your nameserver ? We were talking about servers hosted at Tucows, right ?
Or you are talking about dedicated DNS box that is allocated at our sites and that you "own" exclusively ? Please clarify.
As for the global vs. record TTL, this is how current version of the product works.
The record based TTL must be assigned in any case, so no options here.
As for the ability to change it to a larger value, I can't comment it - Bruce may want to do it.
A DNS lookup may only take you a few milliseconds, but when you're running on a CDPD modem, 19.2K/s with 2-4 SECOND latency (typical while roaming off-network), having to wait an extra 15 seconds for a DNS lookup every 5 minutes is a pain.
On the other hand, when I'm planning an IP change of some sort which cannot have redundancy on two IPs, I usually set my TTL to 60 seconds, that way users experience almost no downtime (a maximum of 60 seconds, so in reality, an average of 30 seconds or less)
