Hi list, So, I imagine that I cannot be the first person to come across this, and maybe someone else here has. At work, we get to our intranet by going to http://intranetname. This name is resolved by WINS. Eventually, we will no longer have a WINS server or be using WINS, and that will be resolved by DNS. The FQDN would be intranetname.ourdomain.com. The problem with that is that by going to the site using the FQDN, IE will interpret that as an IntERnet zone site. We have our security settings on our client machines set differently in the intRAnet zone and the IntERnet zone. So, does anyone know how I can get around that? Here is what I'm currently thinking, and I don't see why this wouldn't work. With DNS, a user can still go to http://intranet. That will still resolve just fine, correct? If so, what I will do is setup an additional site on the intranet server that will redirect users from http://intranet.ourdomain.com to http://intranet, and that would be the end of that. I guess I'm just asking if that seems like a fine solution or if there is some other better/standard way to get around this. Thanks, Ray at work p.s. Site is hosted on a W2K server, hence on topic. :P ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm