<div>
if domain.com is AD domain name, then its expected and there is no option<br />
<br />
You need to keep some prefix like www or any other like corp.domain.com, without that it will not work
</div>


<div>
I was told by web developer that www is stripped for SEO. So we are out of luck? Website won't work inside our network?
</div>


<div>
<i>I was told by web developer that www is stripped for SEO. So we are out of luck? Website won't work inside our network?<br />
</i> Tell the webdev to put it back you need the www or you can't access it inside your network.
</div>


David Barman

<div>
They are saying it effects SEO so it has to be this way. Any web expert to confirm that?
</div>


<div>
I've checked stackoverflow, yoast and a few other sites and the webdev is apparently incorrect. &nbsp;all they have to do is change the redirect 301 to add the www instead of strip. You also have to change the setting in webmaster tools It will not affect your google analytics. &nbsp;Demand proof from them
</div>


<div>
The issue has started since the Exchange has been added? I suppose this Exchange has got a DNS A record with that ip (i.e. the exchange server has been named domain.com and you have a domain.com. A xx.xx.xx.xx in DNS) so that emais get delivered to exchange. <br />
You should put in the DNS mail.domain.com. A xx.xx.xx.xx and &nbsp;mail.domain.com. MX domain.com.
</div>


<div>
You would need to install iis on the DC, and configure it as a proxy to the IP where the site is hosted.<br />
<br />
The other issue, correct the configuration on the web server where the site is hosted yo make www.domain.com&nbsp;as the primary while it Suso knows domain.com for external access without ...<br />
<br />
I.e. Instead of the current setup that the site drops to domain.com, &nbsp;any request will ve ups hitter to www.domain.com&nbsp;resolving your issue...
</div>


<div>
Arnold , i believe that moving the exchange out of the equation would revert the configuration as it was before. What do you think
</div>


<div>
Gaye issue is their AD was setup using the public domain. Exchange is not mil,I aged in the function as it could have been on a .priv suffix, while the domains in exchange used domain.com as the hosted local domain and part of the..<br />
<br />
\\addomain resolves to the ip of the DCs<br />
<br />
The change in the web server config, from possibly serverName donain.com to www.domain.com<br />
Either on the main config, or within the virtualHost entry....<br />
<br />
The only impact for local users they must use the full www.domain.com&nbsp;while everyone outside could use either.
</div>


<div>
Arnold:<br />
<br />
For: The change in the web server config, from possibly serverName donain.com to www.domain.com<br />
Either on the main config, or within the virtualHost entry....<br />
<br />
Is this something to be done on the server hosting the website or something internal to the network. Can you explain further?
</div>


<div>
The server hosting the site is where a web server config change is needed.<br />
I.e. Make the prinary site reference www.domain.com&nbsp;with domain.com as an alias. (serverAlias)<br />
Much depends on how you access the configuration, of the external host. The location of the files does not need to change.<br />
Are you using a CMS Wordpress, joomla, etc. <br />
It might be part of cms settings that rewrite the request to reference domain.com/ as the base. In such a case, the changes within the CMS admin interface to switch from domain.com to www.domain.com&nbsp;is all that is needed.<br />
Much of the time will be to identify the origin where the domain.com reference cones into play.
</div>


<div>
We are not in control of the web server. The web developer states that www needs to be stripped for SEO
</div>


<div>
Not sure i agree &nbsp;with that, <br />
The choice is yours. Do your internal user need to access your public site?<br />
<br />
Setup an internal proxy that is then configured to access the external.......
</div>


<div>
Internal proxy. By what means?
</div>


<div>
You can setup squid-proxy through which all your outgoing non lan traffic will be sent to this server. Depending on your environment, firewall....../router. though the issue is that the use of domain.com necessitates that all workstations are effectively configured to send all access attempts to this proxy server that will .....<br />
<br />
If you have exchange in house, and since &nbsp;you've elected to use the same public domain as you ad domain, what about hosting your website in house?<br />
As pointed out by Mahesh, use of public domain as the ad was originally advised against just for this reason, some recommendation dealt with adding a .local or a non public suffix. the direction has since adjusted to have the AD as a subdomain of the public, i.e. internal.domain.com or local.domain.com that deals with certificate issuers who stopped issuing certs on the .local suffix, or potentially on any unknown/recognized suffix.....<br />
<br />
My question as to the SEO, though possibly harsh, which of the two is more important to you?<br />
1) access of the site by your internal users<br />
2) SEO data<br />
<br />
Here is a reference on once you setup IIS on your DC which is not advisable and with certain version might be prevented which can be setup as a reverse proxy server...<br />
<br />
i.e. any port 80 requests that hits the DC will force it to go out to the IP of your existing external site request the info and present it to the requesting user.<br />
<br />
Instead of IIS, you could install apache, squid-cache configured to listen on port 80 and configured a as a reverse proxy to go out and get the data ...<br />
Note that any time you change the hosting provider or the hosting provider makes changes to where (IP) of the site, you would need to update these systems on all your DCs..........
</div>


<div>
SEO, the big firms do not follow and I believe the various search engines, automatically strip out the www from the URL as it is the common prefix to identify web sites.
</div>


<div>
So when you say they strip the www, that means we don't need to and can leave www and still receive the same SEO effect?
</div>


<div>
Look at bing's or googl's seo guides, IMHO, references to domain.com merely mean it is best to make sure the your site is accessible through both, versus making the site identify as ....<br />
<br />
Often a site reflects the name used by the visitor, though a cms often will assert a preconfigured URL which is why I asked whether you are using such ....<br />
<br />
<br />
My point which has priority in your view, functionality for those on your work LAN, or the. sEO?<br />
<br />
Do your users while at work need to access your public web site got any work related reason?
</div>


<div>
<div class="content wysiwyg-content">
Windows DNS issue. &nbsp;Customer added on-premise Exchange server. &nbsp;Since doing so, their is a problem accessing their public website from within the network. &nbsp;The website is designed to strip the www prefix. When accessing the website www.domain.com&nbsp;it strips it to domain.com. &nbsp;The AD domain is also domain.com so when the website tries to redirect to domain.com it goes to the internal DNS which is the Exchange server. &nbsp;Need assistance in configuring DNS so it continues to route to the public website when the www is stripped and not effecting any Exchange 2016 functionality.
</div>
</div>


Windows DNS issue.  Customer added on-premise Exchange server.  Since doing so, their is a problem accessing their public website from within the network.  The website is designed to strip the www prefix. When accessing the website www.domain.com it strips it to domain.com.  The AD domain is also domain.com so when the website tries to redirect to domain.com it goes to the internal DNS which is the Exchange server.  Need assistance in configuring DNS so it continues to route to the public website when the www is stripped and not effecting any Exchange 2016 functionality.

Redirect domain without prefix to external website.

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.