On 12.01.12 09:09, MontyRee wrote:
I have one question about NS cache ttl.
for example, I can get two different NS TTL like below.
$ dig google.com ns +trace
google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns4.google.com.
;; Received 164 bytes from 192.5.6.30#53(a.gtld-servers.net) in 173 ms
google.com. 345600 IN NS ns4.google.com.
google.com. 345600 IN NS ns1.google.com.
google.com. 345600 IN NS ns2.google.com.
google.com. 345600 IN NS ns3.google.com.
;; Received 164 bytes from 216.239.34.10#53(ns2.google.com) in 43 ms
so, on resolving DNS, which NS record TTL will be cached generally?
172800 or 345600?
afaik, both will be. however the former are just delegation records, so
the latter will override them, snd since delegations will expire
sooner...
(at list bind used to work this way some years ago when I was tracing a
problem)
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"They say when you play that M$ CD backward you can hear satanic messages."
"That's nothing. If you play it forward it will install Windows."
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
