• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 52
  • Last Modified:

Windows 2012 R2 IIs does not work without www of the domain on the browser

We have a problem with the new IIs in Windows 2012 R2. On prior versions of IIs we added two sites point the same IP and port 80 for one domain for the www.anydomain.com and the other for its anydomain.com (without WWW) and worked perfectly when you called the domain with WWW and without WWW. Now in windows 2012 R2, first we can’t add that two sites pointing to same IP and because windows 2012 R2 reject that. Then we added a site www.anydomain.com and inside that site we configured bindings to point port 80, one  both www.anydomain.com and other domain.com, but when we call the page like anydomain.com not work, just work if you put with WWW, in other words, www.anydomain.com

How can we configure the anydomain.com (without WWW), also?

Thank you
0
Alex E.
Asked:
Alex E.
  • 3
  • 2
  • 2
2 Solutions
 
Brian DayhoffSenior Full Stack DeveloperCommented:
This is either an issue with a misconfiguration in your A record on your DNS host, or alternately in your web.config. If the request turns up in your server access log, the issue is your web.config. If it doesn't, it's your DNS host.
0
 
Alex E.Author Commented:
The domain A records are the defaults of godaddy, we don’t have web.config yet in inetpub, the server is almost new.
0
 
Brian DayhoffSenior Full Stack DeveloperCommented:
This sometimes happens when you have nested web.configs that accidentally got stuffed in there somehow. An apache or nginx stack supports nested configurations, however IIS does not, and requires that only one config be located at the web root. A quick grep of your filebase will reveal whether or not that is your issue.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Brian DayhoffSenior Full Stack DeveloperCommented:
I would start off by checking both the server access log and the network tab in your web inspector to determine which server the host header is originating from. If those point to your actual server, then you would also want to look at the error log to reveal your problem. If the host header in the client is wrong and/or there is no entry in your access log, then it's definitely your DNS that is messed up.
0
 
Michael MachieFull-time technical multi-taskerCommented:
As stated above, this could be related to how your Public and Internal DNS records are set up.
Most Hosting providers by default provide a www record that allows www.domain.com to resolve to your domain.
Many times you need to add a record with no www to point to your domain so that anyone not using www. can still reach you.
1
 
Michael MachieFull-time technical multi-taskerCommented:
Hi,

What was the actual issue and fix? This will help others who find this question and answer.
0
 
Alex E.Author Commented:
Fixed the DNS’s

Thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

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