|
|
 |  |
Re: Running on two.From: Ross Markbreiter Date: Tuesday, November 2, 1999
Time: 7:17:00 pm What if you using firewall, NAT does this affect it from working.
Ross
>>Men and Mice, is there something I'm missing? Is there a TTL at play here
>>that makes the client ignore that a secondary exists?
>
>As promised, I have had our engineers examine this issue, and my conjecture was confirmed. This is an Open Transport issue on the client machine, not a server issue. Here's the response I got from our engineers:
>
>We've done some investigation on this and this seems to be plain resolver stupidity.
>
>This is what we did:
>
>Experiment 1
>------------
>Two DNS server IP addresses specified in the TCP/IP control panel. We killed server 1 and every query took 15+ seconds (The resolver tries server 1 for 15 seconds before giving up. This happens for every query.)
>
>Experiment 2
>------------
>Three DNS server IP addresses specified in the TCP/IP control panel. We killed server 1 and 2 and every query took 30+ seconds (The resolver tries both servers, each for 15 seconds, before giving up. This happens for every query.)
>
>We tried this both with Mac OS 8.6 and 9 and got the same results.
>
>Bottom line: The resolver always tries to contact the listed name servers in order, no matter what.
>
>------------
>
>At 5:13 PM -0400 10/29/99, andrew kagan wrote:
>>Thanks, Chris...it wouldn't surprise me if it's a TCP stack issue...I'll try
>>it with a few NT boxes and see what happens.
>
>Have you had a chance to look into this? I would be interested to see if NT (or Linux, or MacOS X Server, or other OS) behaves any better.
>____________________________________________________________________
>Chris Buxton cbuxton@menandmice.com
>Men & Mice http://www.menandmice.com
>Makers of: QuickDNS Pro
|

Return to Digital Point Solutions' Home Page |