Home »

Fixed Domain Name Conflict With Website (Windows Server 2008 R2)

Thursday, June 2, 2011
I recently created a Domain Controller. However, I forgot that it's the same with Website. So when users join to Domain. It cannot connect to real website while the others works well. I don't want to change the domain name of Domain Controller. It's not so good. I think!
I found a temporary solution for this problem. I created a "New Host" in Forward Lookup Zone. I named it "www" and the IP Address is the Public IP of real site.
 

Now, users have add "www" before they want to receive the real one. I know it's inconvenient, but just temporary.  



+ Update: I just found a perfect solution for this using Network Shell. Just a simple command. It works like a charm.

netsh interface portproxy add v4tov4 listenport=80 listenaddress=kenhgiaiphap.vn connectport=80 connectaddress=xxxx

 
Have fun!
Tags: