> > One of the simpler fixes for a Domain Name Server problem is to add a > > number of these to your computer TCP/IP configuration. > > This is good advice - it's always a good idea to have several nameservers > listed in your TCP/IP config. However, I don't think it would help with this > particular problem - if the first nameserver in your list returns stale info > from its cache, then the query was successful (though wrong), and next one in > the list won't be tried, even if your web browser fails to establish a > connection to the address supplied by the first nameserver.
That might be so, but I do know that I have used such a list on computers that could not get an updated site. Once changed, it worked fine. Perhaps there is some code that looks to see if the result is successful? YMMV.. Craig Healy Providence, RI _______________________________________________ IRCA mailing list [email protected] http://montreal.kotalampi.com/mailman/listinfo/irca Opinions expressed in messages on this mailing list are those of the original contributors and do not necessarily reflect the opinion of the IRCA, its editors, publishing staff, or officers For more information: http://www.ircaonline.org To Post a message: [email protected]
