So my set up is the following:
- Windows server 2012 R2
- IIS 8 with ASP 4.5
- Umbraco 7.2.3 (assembly 1.0.5556.26329)
- New website created under IIS with a basic website set up
- DNS records created (both internal and external)
- Correct port forwarding on my firewall
With all this set up, my website test.don-zalmrol.be is accessible from inside my network (LAN) trough the hostname, cname and IP.
From the outside I can access the same URL, but I see the default IIS page.
So what did I've forget to enable so it will reach the Umbrace site instead of the default IIS webpage?
Just to be 100%, have you checked the spelling? (I only ask because in your initial post you said the domain was test.don-zalmrol.be, but in the last post you said you bound test.donzalmrol.be without the hyphen)
Is your bindings IP address correct? I think this should be your servers public IP address (the screenshot shows 10.0.0.8). Your domain is configured to point to 46.30.211.32 so I believe these need to match.
Sorry, I did a DNS lookup on your domain and that's what it said the domain was pointing to. Could just be a delay in the DNS changes taking effect.
The binding setting should be saying "if you find a request on this IP address for this domain, then point it at this site" so I think the IP should need to match the IP that your (sub)domain is configured for AFAIK.
Also, given that turning off the default site resulted in a 404, it would suggest it's an issue with IIS routing the request to the correct site, which an unmatching IP address could cause.
Ok, I see from where the 46.30.212.110 is coming from.
I'm registerd with one.com and it's probably their NS server responding to the request.
Changed those settings on their side now.
But still with or without this, I should still be able to access my site through the cname "test.don-zalmrol.be".
And it does, but ends on the wrong site (in this case the default site). So the problem must be somewhere in the settings of IIS...
Is there any reason your are using a CNAME record? and not an A record for your subdomain? Not sure if it makes a difference, but could be worth a try?
I'm following common practice with just my domain name as the A record (e.g. don-zalmrol.be -> 81.83.30.153) and then a cname (e.g. test.don-zalmrol.be -> don-zalmrol.be)
Shouldn't make any difference, it's just cleaner on a networking level. So if you ever would have to change your public facing IP address, you now only have to do it once and the rest follows :)
But my problem is for what I can see is on the IIS server and not on a networking level.
For some reason it's pointing to the default site instead of the test site.
My DNS was just propagating some small changes to see if the problem would be solved.
But in this case the blue page with a globe and green checkmark are a default page from my Synology NAS.
The url is still test.don-zalmrol.be for testing.
What we know for sure is that the DNS internally and externally are working as they should.
But for some reason the IIS server is returning the default webpage. So on the IIS there is an internal routing problem.
It started working last night (see 5 posts back ;)). It would seems strange to be the worker process as these usually recycle whenever you make a change that needs an App Pool recycle so not sure how that is the culprit. My best bet is still on the server caching your DNS settings and thus associating your test domain with the old IP address untill it's cache was flushed and the DNS was re-fetched.
Either way, I'm glad you managed to get it working.
Umbraco + IIS8 outside access
Hi everybody,
So my set up is the following: - Windows server 2012 R2 - IIS 8 with ASP 4.5 - Umbraco 7.2.3 (assembly 1.0.5556.26329) - New website created under IIS with a basic website set up - DNS records created (both internal and external) - Correct port forwarding on my firewall
With all this set up, my website test.don-zalmrol.be is accessible from inside my network (LAN) trough the hostname, cname and IP.
From the outside I can access the same URL, but I see the default IIS page. So what did I've forget to enable so it will reach the Umbrace site instead of the default IIS webpage?
Anybody any clues?
Thank you in advance.
Laurens
Have you configured the IIS Host Header for your domain?
https://technet.microsoft.com/en-gb/library/cc753195%28v=ws.10%29.aspx
Matt
Hi Matt,
Yes, I did bind the hostname with the site in IIS.
Test.donzalmrol.be bind with my internal server ip on port 80 as http.
Cheers,
Laurens
Just to be 100%, have you checked the spelling? (I only ask because in your initial post you said the domain was test.don-zalmrol.be, but in the last post you said you bound test.donzalmrol.be without the hyphen)
Matt
Hi Matt,
Sorry, my previous post was done via my cell phone. It is with a hyphen in the middle.
Here is a picture of the bindings on my server.
Have you tried stopping the default site to see if that changes anything?
Is your bindings IP address correct? I think this should be your servers public IP address (the screenshot shows 10.0.0.8). Your domain is configured to point to 46.30.211.32 so I believe these need to match.
My external ip is 81.83.30.153. From where do you get the 46.30.211.32 address?
If I disable the default site, I get a 404 page. Pointing the address to my external IP? I can try it. But my dns should be able to resolve it.
Changed it to my external. But now the IIS is showing as well in the local domain. So I don't think this is the solution.
Sorry, I did a DNS lookup on your domain and that's what it said the domain was pointing to. Could just be a delay in the DNS changes taking effect.
The binding setting should be saying "if you find a request on this IP address for this domain, then point it at this site" so I think the IP should need to match the IP that your (sub)domain is configured for AFAIK.
Also, given that turning off the default site resulted in a 404, it would suggest it's an issue with IIS routing the request to the correct site, which an unmatching IP address could cause.
Ok, I see from where the 46.30.212.110 is coming from. I'm registerd with one.com and it's probably their NS server responding to the request.
Changed those settings on their side now. But still with or without this, I should still be able to access my site through the cname "test.don-zalmrol.be". And it does, but ends on the wrong site (in this case the default site). So the problem must be somewhere in the settings of IIS...
Is there any reason your are using a CNAME record? and not an A record for your subdomain? Not sure if it makes a difference, but could be worth a try?
I'm following common practice with just my domain name as the A record (e.g. don-zalmrol.be -> 81.83.30.153) and then a cname (e.g. test.don-zalmrol.be -> don-zalmrol.be)
Shouldn't make any difference, it's just cleaner on a networking level. So if you ever would have to change your public facing IP address, you now only have to do it once and the rest follows :)
But my problem is for what I can see is on the IIS server and not on a networking level. For some reason it's pointing to the default site instead of the test site.
Have you changed something else then? as I've just tested your domain and it's now showing your umbraco site.
Maybe it's just that your servers DNS settings weren't updated yet so it wasn't routing your CNAME to your server?
My DNS was just propagating some small changes to see if the problem would be solved. But in this case the blue page with a globe and green checkmark are a default page from my Synology NAS.
The url is still test.don-zalmrol.be for testing.
What we know for sure is that the DNS internally and externally are working as they should. But for some reason the IIS server is returning the default webpage. So on the IIS there is an internal routing problem.
DNS checks: - External nslookup test.don-zalmrol.be 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8
Non-authoritative answer: Name: test.don-zalmrol.be.don-zalmrol.be Address: 81.83.30.153
- Internal nslookup test.don-zalmrol.be Server: UnKnown Address: 10.0.0.10
Name: test.don-zalmrol.be Address: 10.0.0.8
Thank you for your help so far, Matt :)
I'm going to bed, let's pick this up tomorrow.\
It's probably something silly.
Ok, so after testing now, it seems to be working. I didn't changed anything this night and just tested it when I've arrived in the office.
A colleague of mine is thinking it was the IIS worker process on the old application pool from the default site still hogging all the traffic.
So after it's time was up, the worker did a recycle operation and cleared the system. Now it's all working :)
Thank you for your help Matt.
For those with the same issue, you can try forcing the worker to recycle. https://technet.microsoft.com/en-us/library/cc770764(v=ws.10).aspx
Cheers,
Laurens
Hey Laurens,
It started working last night (see 5 posts back ;)). It would seems strange to be the worker process as these usually recycle whenever you make a change that needs an App Pool recycle so not sure how that is the culprit. My best bet is still on the server caching your DNS settings and thus associating your test domain with the old IP address untill it's cache was flushed and the DNS was re-fetched.
Either way, I'm glad you managed to get it working.
Matt
Ah ok, I thought you where talking about the Synology webpage. My mistake. Could be, could be both.
is working on a reply...