Actually, that article was written with reference to an internal DNS server that can also resolve external names. You are correct that if DNS is installed on Win2K, you don't have the option to leave the primary DNS server entry blank. Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/pages/author_index.asp?aut=3 http://isatools.org Read the help / books / articles! ----- Original Message ----- From: "Han Valk" <Han.Valk@xxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Tuesday, December 10, 2002 1:11 AM Subject: [isalist] Question about the "DNS for ISA Server" article by Jim Harrison http://www.ISAserver.org Hi, The above article shows a solution for ISA-Only DNS. That's where DNS runs on the ISA server. It says that the DNS entry in the properties of the external interface should be empty. But that is not possible. If you run Microsoft DNS on a Windows 2000 server and you don't put a DNS server entry in the properties of an interface (internal or external) Windows will do it for you (127.0.0.1) and there's no way of stopping it so there will be an entry for the external interface. Is this an 'error' in the article? Causes an entry like this any problems? Any way to get rid of it? Best regards, Han Valk ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')