Whatever Netscape is doing with their server at 205.188.247.66 since 9:00a EST I really don't know, but it's down hard and its starting to generate significant customer feedback. Their own nameservers all seem to agree that www.netscape.com is CNAME'd to vwww-va2.netscape.com (which has the above IP) at this time, while ns.cw.net (their secondary) seems to think it's CNAME'd to www-ld1.netscape.com , with an A record of 207.200.75.200, which is actually responsive. Sometimes after 10:00a EST, this started to generate significant support calls. Currently trying to populate the DNS caches around here with the working version, which is tricky given that 3 out of 4 NS point to the dead CNAME. bye,Kai -- kai@conti.nu "Just say No" to Spam Kai Schlichting Palo Alto, New York, You name it Sophisticated Technical Peon Kai's SpamShield <tm> is FREE! http://SpamShield.Conti.nu | | LeasedLines-FrameRelay-IPLs-ISDN-PPP-Cisco-Consulting-VoiceFax-Data-Muxes WorldWideWebAnything-Intranets-NetAdmin-UnixAdmin-Security-ReallyHardMath