[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] dns and nameservers
- Subject: Re: [cobalt-users] dns and nameservers
- From: Jens Kristian Søgaard <jens@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun Apr 15 04:05:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hi Dan,
> > 1) Browsers never do resolves on their own (well, I have yet to
> > see one that
> > does) - this is handled by resolve libraries.
> IIRC, MSIE caches DNS info.
Oh yeah, that's probably right. MSIE is known to do weird things :-)
> > 2) There is no rule that the primary server should be asked
> > first. It is the nameserver with the fastest reply that is contacted
first! (i.e.
> > so you will presumeably ask the name server that is geographically near
to yourself)
> Usually your ISP's nameserver, unless you configured your system to use
> another DNS so that things like .travel or .biz domain names resolve.
Well, I was ofcourse talking about the nameserver that does the lookups -
yes. If a user sets that to be his ISP's nameserver, then that will be the
one... I have a caching nameserver (bind 9) on my LAN that does this.
--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@xxxxxxxxxxxxxxxxxxxx,
http://www.mermaidconsulting.com/