"GriffithsJ" wrote:
<!--SNiP-->
You're probably going to catch hell for this post since you posted to
microsoft.public.windows.server.dns
microsoft.public.win2000.dns
microsoft.public.scripting.vbscript
microsoft.public.vb.general.discussion
microsoft.public.inetserver.asp.general
microsoft.public.inetserver.misc
Unless your web servers are running on W2K, this does not have anything to
do with:
microsoft.public.win2000.dns
These definitely do NOT have anything to do with DNS:
microsoft.public.scripting.vbscript
microsoft.public.vb.general.discussion
microsoft.public.inetserver.asp.general
This one really doesn't either but it is server related:
microsoft.public.inetserver.misc
That leaves us with this;
microsoft.public.windows.server.dns
It is also not really a DNS question since it is a philosophy or methodology
question related to host name naming practices. It should fall more into
the security arena because adding the server name to your URL is a security
issue. Your servers should be behind firewalls. Your internal DNS can have
anything it wants but external should only have public domain naming.
Please only follow up in m.p.window.server.dns
--
Roland
This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
-Technet Knowledge Base-
http://support.microsoft.com/default...&ln=EN-US&FR=0
-Technet Script Center-
http://www.microsoft.com/technet/tre...er/default.asp
-WSH 5.6 documentation download-
http://www.microsoft.com/downloads/d...displaylang=en
-MSDN Library-
http://msdn.microsoft.com/library/default.asp