[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

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.com 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.com - also the host header in IIS is extranet.externaldomain.com

Can anyone give me a pointer here. TIA
0
petervane
Asked:
petervane
  • 3
  • 2
1 Solution
 
mb042Commented:
Do a ping from an external box to confirm that the public DNS (for extranet...) does contain the correct record.
0
 
mb042Commented:
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.
0
 
petervaneAuthor Commented:
Thanks for that.

The address itself resolves correctly. In other words pinging extranet.externaldomain.com 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.com 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.com ---- However it seems to make no difference other than now I can internally resolve extranet.externaldomain.com to the local server.

Once again help is much appreciated.
0
 
mb042Commented:
the host header needs to be the full external dns name.
Is this SBS premium? If you have installed ISA, I would say it is a configuration fault in your server publishing rule.
Also go to
C:\WINDOWS\system32\LogFiles\W3SVC1
find the latest log file and see if that gives you any tips as far as the source request.
0
 
petervaneAuthor Commented:
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
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now