Hello,I am looking to set up a bogus DNS serverfor my test applications. For example, I want users to log into this terminal server called Server_A. Within Server_A, if usersentered the URL ofhttp://test.net or http://myapplication.net, it would go to my local test web server hosting the site (server called Server_B) instead of goingonto the outside world in which we have that two sites hosted on different servers. I need to havethe gatewayturnon theterminal serverfor internet access.I tried doing the conventional change ofhost filebut don't have any luck with such http pages. The site is built around so many embedded link, images. I figure I tried the bogus dns to see if I have any luck.I plan toinstall a standalone DNS server called Server_C. On my terminal server I will point toServer_C as my dns server. I am not sure how the entry would be on the DNS server. Add cname in? How do I specify the http://test.net or http://myapplication.netthanks,tnt

Hello, Sound like what you are looking for is a split brain DNS... http://blogs.techrepublic.com.com/networking/?p=1362 Just add an A-record in the zone for www.test.net that resolves to the internal test server Example A record test.net -> 192.168.x.x A record www.test.net -> 192.168.x.x You could also use C Names as well for www, mail, etc. There are easier ways to accomplish this. I am suggesting split brain because you mentioned that (a) test.net is already a domain name in the public namespace and (b) you have a lot of hard coded links in your app/site that refer to http://test.net. If the above conditions are true, split brain is the way to go. Otherwise, use host headers and your existing DNS to do it. Just add a zone in your DNS server for test.local as well as a host header in your IIS site for test.local. Then users can go to http://test.local to browse the internal test site. Miguel Miguel Fra / Falcon ITS Computer and Network Service and Support , Miami, Fl