which NS record will be cached?

Peter Andreev andreev.peter at gmail.com
Thu Jan 12 10:22:18 UTC 2012


2012/1/12 MontyRee <chulmin2 at hotmail.com>

>
> Hi, all.
>
>
> 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?
>
>
> Thanks in advance.
>

345600


> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>



-- 
--
AP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20120112/330eefd6/attachment.html>


More information about the bind-users mailing list