Re: [cobalt-users] Making TTL @ my nameserver synchronize with parents

[Jeff Lasman <blists@xxxxxxxxxxxxx>]

On Saturday 14 February 2004 09:08 am, Al-Juhani wrote:

> May be slightly off-topic but someone here might help in this.
>
> My own nameservers has TTL values of 86400 seconds [24 HRS]
> Parent Servers (gtlds) when contacted report 172800 seconds [48 HRS]
>
> Do I need to change my TTLs to 172800 to match the parents or
> is there any other way to go around this.

The definitive discussion on this issue has been going on during the 
last several days on the Bind Users mailing list, which is also 
gatewayed to the comp.protocols.dns.bind newsgroup.

Here's a short part of the thread, that will hopefully clear things up a 
bit:

<snip>
In article <c0tk8d$hai$1@xxxxxxxxxxx>,
 Jeff Lasman wrote:

> On Sunday 15 February 2004 06:44 pm, R. Scott Perry wrote:
> 
> > It seems that the real problem is with NS A records that have a TTL
> > that differs from the NS records.  But, if there is a NS TTL
> > discrepancy, there is likely a TTL difference between the NS record
> > and the NS's A record.
> 
> Are you writing that if my NS records and A records for
> ns1.exmaple.com 
> have the same TTL I'm okay in spite of what dnsreport says?

Yes.  Hardly anyone uses the same TTLs as the TLD servers do, but they 
usually have consistent TTLs within their zones.  The Internet hasn't 
come to a screaching halt yet.
<snip>

You can't change what the root servers have for TTL on your NS records.  
It's set in stone at two days.

What you should do is make sure that your NS records and A records for 
your nameservers (nsX.example.com) have the same TTLs.

And live with the error message as reported by dnsreport.com, as the 
rest of us are doing.

Or switch both the NS records and A records for your nameservers to two 
days.

Most of us don't change our nameserver IP#s daily, and two days is 
probably fine for them.

Note that while the list and the newsgroup are sponsored by isc.org, the 
authors of Bind, the posts do not represent any official opinion.

However, none of the people at ISC themselves have written back with any 
different information, which they usually do if someone writes 
something incorrect.

Personally, I'm changing our NS and A records for our nameservers for 
two days, just to avoid seeing the errors, but I have no problem 
changing them back a few days in advance of any nameserver move.

Jeff
-- 
Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA  92517 US
Professional Internet Services & Support / Consulting / Colocation
Our blists address used on lists is for list email only
Phone +1 909 324-9706, or see: "http://www.nobaloney.net/contactus.html";