By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Were you correct?
like some valley cheese,
local, but prized elsewhere."
- W.H. Auden
Today's Know-IT-All answer is:
d. All of the above
Learn more:Normally, when Windows 2000 is used for Internet Connection Sharing, the default is to have Windows use the ISP's DNS servers rather than any local servers. This can be problematic; many people who use remote-hosted DNS servers complain about constant outages or lookup failures. Even though Windows 2000 Workstation (as well as other Microsoft desktop OSes) cache DNS lookup information, they don't do so with a great deal of robustness, and so perform lookups quite often. If an ISP's DNS server is exceptionally burdened, the lookups can time out.
Windows 2000 Server comes with its own DNS server, which performs hostname lookups (and registers DNS entries for Active Directory). It is, however, sometimes too much of a burden for a smaller machine that is only being used as a routing server. Some administrators may want to install a third-party DNS server on Windows, an implementation of BIND that is not as burdensome in size or system resources.
Do you have an idea for an admin Know-IT-All question? Let Mr. Know-IT-All know!