Redirect requests to external domain to an internal server
Windows 2003 domain
DNS AD integrated Zone.
internal Zone name: companyA.com
We had a site hosted outside named "companyB.com". We decided to host this site in our network, so we made the changes in the external DNS zone of "companyB.com" to point to this site with a Public IP that is part of the subnet assigned to us by our ISP. When our internal users try to access "companyB.com" they can't. I created an "A" record in the internal "companyA.com" zone trying to redirect the internal requests to the internal IP of the server where the side is hosted but it would not work. To make it work our user would need to type http://companyB.com.companyA.com instead of http://companyB.com . Question:
Could I create another primary zone in our internal DNS(AD integrated perhaps?) called "companyB.com" , then create the www record that points to the internal server? then our users would get redirected to the internal site without trying to access this site extermally? I am not sure about creating another primary forward lookup zone for a zone that we do not host in the same DNS server integrated with Active Directory
Thanks
Thanks in advance for your help,
John
DNS AD integrated Zone.
internal Zone name: companyA.com
We had a site hosted outside named "companyB.com". We decided to host this site in our network, so we made the changes in the external DNS zone of "companyB.com" to point to this site with a Public IP that is part of the subnet assigned to us by our ISP. When our internal users try to access "companyB.com" they can't. I created an "A" record in the internal "companyA.com" zone trying to redirect the internal requests to the internal IP of the server where the side is hosted but it would not work. To make it work our user would need to type http://companyB.com.companyA.com instead of http://companyB.com . Question:
Could I create another primary zone in our internal DNS(AD integrated perhaps?) called "companyB.com" , then create the www record that points to the internal server? then our users would get redirected to the internal site without trying to access this site extermally? I am not sure about creating another primary forward lookup zone for a zone that we do not host in the same DNS server integrated with Active Directory
Thanks
Thanks in advance for your help,
John
ASKER
giltjr,
Thanks for your answer. Does it matter if it is AD integrated or not? . In regard to " For any host name in that zone that you access from inside your network you will need to add that host name to your companyB.com zone." you mean like if it later we decide to create a different site like : "customer.companyb.com" , then
- if we host it outside we would need to point that internal A record in that zone to whatever was pointed to in the external DNS zone.
- If we host it inside then we would do the same as what you suggested in your first part of the reply above.
Again, I am making sure I understood your reply and please clarify if this new primary lookup forward zone should be AD integrated or not? does it matter either way?
Thanks
John
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It worked. thanks!
ASKER
This expert is even willing to help during weekends and Christmas season on top of it. Very few of them of the experts do that.
However, you will need to add other A records for companyB.com. For any host name in that zone that you access from inside your network you will need to add that host name to your companyB.com zone.