petervane
asked on
Multiple Domain Extranet Site
Have an extremely simple extranet page I wish to place on the internet from a non production server.
I have created a website in Sharepoint using a host header and I have created DNS records. The website is in the form of extranet.externaldomain.co m where externaldomain.com is actually hosted elsewhere.
The page resolves correctly internally but externally I always end up at the default website. I have created a new zone in DNS and created an A record to point to the server address for extranet.externaldomain.co m - also the host header in IIS is extranet.externaldomain.co m
Can anyone give me a pointer here. TIA
I have created a website in Sharepoint using a host header and I have created DNS records. The website is in the form of extranet.externaldomain.co
The page resolves correctly internally but externally I always end up at the default website. I have created a new zone in DNS and created an A record to point to the server address for extranet.externaldomain.co
Can anyone give me a pointer here. TIA
Do a ping from an external box to confirm that the public DNS (for extranet...) does contain the correct record.
Actually didn't read it closely enough.... if you created a new zone, that means your external records are not correct. Get your external DNS host to add the 'A' record for your public IP.
ASKER
Thanks for that.
The address itself resolves correctly. In other words pinging extranet.externaldomain.co m resolves to the server address. So I am getting back to the server which I note I ddnt explain is an SBS server. However the website which shows up is the default website ie not the one I created.
I understand this behaviour is exactly what happens if IIS cannot resolve the host header to an appropriate website it just uses the default website. It is as though the host header information is completely ignored.
Now remember the address extranet.externaldomain.co m is not the domain of this SBS. Let us say it is sbsdomain. Thus I thought I would have to have another DNS zone for externaldomain.com containing A records for extranet.externaldomain.co m ---- However it seems to make no difference other than now I can internally resolve extranet.externaldomain.co m to the local server.
Once again help is much appreciated.
The address itself resolves correctly. In other words pinging extranet.externaldomain.co
I understand this behaviour is exactly what happens if IIS cannot resolve the host header to an appropriate website it just uses the default website. It is as though the host header information is completely ignored.
Now remember the address extranet.externaldomain.co
Once again help is much appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
I resolved the problem....in the host header entry I had the internal NIC address rather than the NIC on the WAN side. All OK now.
I will assign you the points because all you were saying was correct information
I resolved the problem....in the host header entry I had the internal NIC address rather than the NIC on the WAN side. All OK now.
I will assign you the points because all you were saying was correct information