Congratulations on getting Named working, but it seems to me that is
causing more problems presently when you are using a dialup connection. If
you like the idea of cached domain names I believe squid will cache the dns
lookups.. when it runs it has a few "dnsserver" processes running under it.
If you run a DNS for another reason i'm not really sure on an answer.
josiah
> Now I understand, but I cannot do this, because I run DNS on my Linux
> machine. So the client gets immediate answer from the local DNS (when the
> searched host is already known, which is often the case) and then tries to
> contact the remote server. It is at this step that the diald link is
> activated, and the actual packets that get lost are the attempts from the
> client to contact the remote server, not the DNS query.
>
> OTOH, and paradoxally, if the client asks for a Web page which address is
> unknown to my local DNS running on the Linux box, it is named on the Linux
> box that will trigger diald. In this situation, it works immediately!
> Because the client is waiting for named to answer its DNS query, and
> apparently named will try to contact several of the "root name servers" in
> turn, which makes it unimportant if the first packets get lost. Named will
> try until it gets some answer, then it passes the answer to the client
which
> will now contact the remote server. But at this time, the ppp link is
> already up, and it will work just good.
>
> So, the "packets lost" problem is only annoying when the client asks for a
> page already known to my DNS. But this is the case 98% of the times, as
the
> "default home pages" are of course known to the DNS from the first
> connection on, as well as the pages that we consult the most...
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
