Shrinking TTL or ??

[Bill Manning]

It might be worthwhile to note that this list is "BIND-USERS"
and ought to focus on BIND.  This question is related to ultraDNS,
which is an implementation that is genetically unrelated to BIND, e.g.
no shared code. 

The ultraDNS implementation involves effectivly transparent sharing
of diverse hardware.  In the backchannel, updates occur between servers.
Hence the differing TTL.  You hit another machine in the ultraDNS
flotila.

For more detail  www.ultradns.com



> 
> In the zone below, ns1.ultradns.net is the master.   In the 
> additional section of the master it shows:
> 
> ns1.ultradns.net.       1D IN A         204.69.234.1
> 
> But in the additional section of one of the slaves it shows:
> 
> ns1.ultradns.net.       17h34m16s IN A  204.69.234.1
> 
> Why the lower value, what does this signify?
> 
> Also, what factor determine the order in which the servers are listed 
> in the authority or additional section of these dig inquiries?
> 
> 
> 
> glr:/var/named/pz# dig @ns3.mn.cap.gov cap.gov
>  dig @ns3.mn.cap.gov cap.gov
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
> ;; QUERY SECTION:
> ;;      cap.gov, type = A, class = IN
> 
> ;; ANSWER SECTION:
> cap.gov.                1D IN A         198.88.0.19
> 
> ;; AUTHORITY SECTION:
> cap.gov.                1D IN NS        ns2.ultradns.net.
> cap.gov.                1D IN NS        ns1.ultradns.net.
> cap.gov.                1D IN NS        NS4.TN.cap.gov.
> cap.gov.                1D IN NS        NS3.MN.cap.gov.
> cap.gov.                1D IN NS        NS1.cap.gov.
> 
> ;; ADDITIONAL SECTION:
> ns2.ultradns.net.       17h34m16s IN A  204.69.234.2
> ns1.ultradns.net.       17h34m16s IN A  204.69.234.1
> NS4.TN.cap.gov.         1D IN A         207.152.31.3
> NS3.MN.cap.gov.         1D IN A         209.98.47.196
> NS1.cap.gov.            1D IN A         198.88.0.19
> 
> ;; Total query time: 1465 msec
> ;; FROM: glr to SERVER: ns3.mn.cap.gov  209.98.47.196
> ;; WHEN: Wed Oct 27 12:12:32 1999
> ;; MSG SIZE  sent: 25  rcvd: 229
> 
> 
> dig @ns1.ultradns.net cap.gov
> 
> ; <<>> DiG 8.2 <<>> @ns1.ultradns.net cap.gov 
> ; (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: 1, AUTHORITY: 5, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      cap.gov, type = A, class = IN
> 
> ;; ANSWER SECTION:
> cap.gov.                1D IN A         198.88.0.19
> 
> ;; AUTHORITY SECTION:
> CAP.GOV.                1D IN NS        NS1.CAP.GOV.
> cap.gov.                1D IN NS        NS3.MN.CAP.GOV.
> cap.gov.                1D IN NS        NS4.TN.CAP.GOV.
> cap.gov.                1D IN NS        ns1.ultradns.net.
> cap.gov.                1D IN NS        ns2.ultradns.net.
> 
> ;; ADDITIONAL SECTION:
> ns1.ultradns.net.       1D IN A         204.69.234.1
> ns2.ultradns.net.       1D IN A         204.69.234.2
> 
> 


-- 
--bill