Re: TTL for name servers

2012-06-06 Thread Peter Andreev
2012/6/6 Mark Andrews > > In message c...@mail.gmail.com> > , Alexander Gurvitz writes: > > Hi. > > > > TTL returned by YOUR zone authoritative server will (at least should) be > > preferred by caches. > > > > Matt Larson from verisign explained on these: > > > > http://www.merit.edu/mail.archiv

Re: TTL for name servers

2012-06-05 Thread Mark Andrews
In message , Alexander Gurvitz writes: > Hi. > > TTL returned by YOUR zone authoritative server will (at least should) be > preferred by caches. > > Matt Larson from verisign explained on these: > > http://www.merit.edu/mail.archives/nanog/2004-07/msg00255.html > > Regards, > Alexander Gurvit

Re: TTL for name servers

2012-06-05 Thread Alexander Gurvitz
Hi. TTL returned by YOUR zone authoritative server will (at least should) be preferred by caches. Matt Larson from verisign explained on these: http://www.merit.edu/mail.archives/nanog/2004-07/msg00255.html Regards, Alexander Gurvitz, net-me.net ___ P

Re: TTL for name servers

2012-06-05 Thread Peter Andreev
Just to clarify, let's assume that you maintain zone example.be. Let's also say that in .be zone TTL for your NS'es is 86400 and TTL for NS'es in your zone is 345600. In such scenario the latter will be cached by resolver because it is the authoritative data. For some resolver implementations this

TTL for name servers

2012-06-05 Thread hugo hugoo
Dear all, Can anyone clarify to me the use of the TTL for a NS record? Let’s take the example of a *.be domain. A TTL value is present on both locations. 1) In a dns.be server (for example x.dns.be): in my example here below, value is 86400 2) In the name server itself: in my examp