SUMMARY: dns problems with communicator in DU 4.0b

From: George Michaelson <ggm_at_dstc.edu.au>
Date: Wed, 07 Jan 1998 09:32:38 +1000 (EST)

Summary: Netscape Communicator definately has problems. They can
                be *partially* fixed by setting MOZILLA_NO_ASYNC_DNS
                as an env var before running communicator.

                Digital know about this (for some meaning of 'know') and
                may be discussing it with Netscape. No fix promised.

                bind is not at fault. FYI, debugging DNS problems is greatly
                aided by using (a) current spec bind (8.1.1) and (b) using
                its runtime debug options to produce DNS traces of the servers
                view of client calls into its services.

cheers
        
        -George
Received on Wed Jan 07 1998 - 00:32:52 NZDT