google-public-dns not set "max-cache-ttl" ?
9 views
Skip to first unread message
Joint Wang
Jan 12, 2010, 10:13:42 PM1/12/10
to public-dns-discuss
As a test,I create a record: ttltest.slhy.net,set ttl to 99999999,
other name server 's response ttl is 604800 (7 days),but google-public-
dns-a.google.com and google-public-dns-b.google.com answer is actual:
99999999. I think the google's public dns not set "max-cache-ttl"
option as bind 9. this may make longer "dns cache poison".
other name server 's response ttl is 604800 (7 days),but google-public-
dns-a.google.com and google-public-dns-b.google.com answer is actual:
99999999. I think the google's public dns not set "max-cache-ttl"
option as bind 9. this may make longer "dns cache poison".
Windows nslookup command:
nslookup
> server 8.8.8.8
> set debug
> ttltest.shly.net
> server 8.8.4.4
> ttltest.slhy.net
Reply all
Reply to author
Forward
0 new messages