# [EMAIL PROTECTED] / 2003-02-12 14:43:37 +0100:
> On Wednesday 12 February 2003 13:15, Daniel Bye wrote:
> > At a shell prompt, try
> > $ time host doubleclick.net
>
> $ time host dk.doubleclick.net
> dk.doubleclick.net mail is handled (pri=10) by relay2.doubleclick.net
> dk.doubleclick.net mail is handled (pri=10) by relay1.doubleclick.net
>
> real 0m0.269s
> user 0m0.000s
> sys 0m0.005s
>
> $ time host dk.doubleclick.net
> dk.doubleclick.net mail is handled (pri=10) by relay1.doubleclick.net
> dk.doubleclick.net mail is handled (pri=10) by relay2.doubleclick.net
>
> real 0m0.009s
> user 0m0.004s
> sys 0m0.001s
>
> So, it's safe to assume my cache is working? ... and perhaps, resolving
> doubleclick.net et al isn't the issue?
>
> But looks like the cache expires after a couple of minutes?
That's something you can easily check by trying to resolve the name
a couple of minutes later. :)
But that would be a lame test, and you wouldn't really know any hard
data. This is authoritative:
roman@freepuppy ~ 1011:1 > dnsq a doubleclick.net ns2.dcny.doubleclick.net|grep
^answer
answer: doubleclick.net 300 A 199.95.206.210
roman@freepuppy ~ 1012:0 >
so yes. the A RR for doubleclick.net has TTL of 300 seconds.
somewhat stupid if you ask me.
I would suggest you to configure your DNS cache so that it forwards
queries to your ISP's caches. That'll buy you some time.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
