Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Situation: current website is "http://extranet" i would like to change this to "" this site is configured on the same server where the IIS, DHCP and DNS is. i would like to change the sitename to "http://extranet.domainname.COM" but know that the domain is a "domainname.LOCAL" so how do i make shure i can type

thank you in advance!


share|improve this question
I took a shot at the answer, but you really need to provide more information about the network, DNS, firewall, domain, and intended use. – tomjedrz Jun 9 '10 at 0:53

Is your DNS server an authoritative name server for the domain? Then simply add an A or CNAME record to your DNS entries and point it to the IP address or an alternate fully qualified hostname of your server. Once you do that go into IIS, find the website and add the hostname to the website filter.

share|improve this answer

OK, here we go. I am making assumptions (which I shall state). Please clarify in these areas by EDITING YOUR QUESTION rather than commenting.

A1- The website works internally.
A2- You want the website to work across the internet.
A3- The domain "" already exists on the internet.

First, you need to identify an external IP address for the extranet, and you need to setup NAT on your firewall to router traffic from that external IP address to the actual server. How this is done depends on the firewall, but is a standard firewall function. Look in the firewall documentation, on their site, or search here for NAT and the firewall.

Then, you want to add a CNAME record to the internal DNS to map "" to "extranet" (or "extranet.domainname.local"). This should make the FQDN work internally.

Finally, you need to add an "A record" to the "" internet DNS zone mapping "" to the external IP address created above. Whoever administers the "" domain can do this. This should (after a delay of a few hours) make the external access work properly.

Hope this helps.

share|improve this answer

well thanks for the support, i found it... the domain name is a ".local" so i had so make a new zone.. the now zone had the same name juist ".com" so i had two zones, "mysite.local" and a "" afther i did that i had to make a new A record in the new zone, with name and the ipadress of the server wich mysite is on. then i go back to the IIS and change the header of the site to "" port 80 and the right IP. that worked for me fine!

thanks for the help and efforts!


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.