National/International link

[Barry Margolin]

In article <9vla83$n3m at pub3.rc.vix.com>,
Cecilia Cabrera  <ccabrera at ccc.uba.ar> wrote:
>> Other than that, I don't see a good solution.  The problem is that the TTL
>> of the .ar NS records are only 1 hour. 
>
>Not really, it's set to a day (1 hr is the retry time). This leads me the
>following: why isn't my NS caching it for 1 day? I'm thinking maybe it's
>the size of the cache. Is this configurable?

The delegation records from the root servers have 2-day TTLs, but the NS
records on the authoritative servers have 1-hour TTLs.  Here's what I get
from the primary server:

% dig ar ns @athea.ar

; <<>> DiG 8.3 <<>> ar ns @athea.ar 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 10
;; QUERY SECTION:
;;	ar, type = NS, class = IN

;; ANSWER SECTION:
ar.			1H IN NS	ns.ripe.net.
ar.			1H IN NS	uucp-gw-1.pa.DEC.COM.
ar.			1H IN NS	uucp-gw-2.pa.DEC.COM.
ar.			1H IN NS	relay1.mecon.ar.
ar.			1H IN NS	ns1.retina.ar.
ar.			1H IN NS	merapi.switch.ch.
ar.			1H IN NS	ns.UU.net.
ar.			1H IN NS	athea.ar.
ar.			1H IN NS	ctina.ar.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.