unable to access external website from internal AD domain
I have a website configured using Wordpress (www.wordpress.com) as the provider and it is accessible just fine from outside the network. However, when users try to access it at the office from the internal network, they're unable to access the website.
For example, the domain name is ABC.COM and the website address is www.abc.com . I don't have an A record created on the internal DNS zone because this simply won't work. Wordpress doesn't allow for this simple functionality as they do not have a single IP address for me to point to. They do not allow mapping of the "WWW" subdomain. See here http://en.support.wordpress.com/domains/map-subdomain/
The reason this works externally is because I'm using Wordpress DNS servers (i.e. ns1.wordpress.com) for name resolution. I'm not sure that I can do the same inside the office, I'm afraid it will interfere with other internal name resolutions that are working just fine.
So the bottom line is that I need to figure out how to be able to query the Wordpress DNS servers just for the WWW record.
For example, the domain name is ABC.COM and the website address is www.abc.com . I don't have an A record created on the internal DNS zone because this simply won't work. Wordpress doesn't allow for this simple functionality as they do not have a single IP address for me to point to. They do not allow mapping of the "WWW" subdomain. See here http://en.support.wordpress.com/domains/map-subdomain/
The reason this works externally is because I'm using Wordpress DNS servers (i.e. ns1.wordpress.com) for name resolution. I'm not sure that I can do the same inside the office, I'm afraid it will interfere with other internal name resolutions that are working just fine.
So the bottom line is that I need to figure out how to be able to query the Wordpress DNS servers just for the WWW record.
add forwarders to your dns.. i.e. 8.8.8.8
ASKER
I tried configuring a CNAME record but that didn't work because Wordpress strips the WWW from the name.
I already purchased the domain mapping for $13/year. I had to do that in order to be able to access "www.mydomain.com" in the first place.
I also tried forwarders, still not working.
I already purchased the domain mapping for $13/year. I had to do that in order to be able to access "www.mydomain.com" in the first place.
I also tried forwarders, still not working.
Sorry, I missed where it is working externally, so you must already have the CName record in place with whomever manages your public DNS.
Where you have SBS, there should be no need to configure anything internally if www.YourDomain.com works outside of the LAN.
This assumes internally you are using the default yourdomain.local, and you have not added a forward lookup zone for yourdomain.com
SBS would have created a default forward lookup zone for remote.yourdomain.com which is OK.
If this is the case all DNS queries for anything but remote.yourdomain.com should be forwarded to the internet based DNS servers, the same as for any remote user.
I have this exact config, and it works fine.
Might you have an internal yourdomain.com forward lookup zone in place on the SBS? If so we will need to configure or remove it. (do not remove remote.yourdomain.com or what ever you use for external connections to the SBS)
Where you have SBS, there should be no need to configure anything internally if www.YourDomain.com works outside of the LAN.
This assumes internally you are using the default yourdomain.local, and you have not added a forward lookup zone for yourdomain.com
SBS would have created a default forward lookup zone for remote.yourdomain.com which is OK.
If this is the case all DNS queries for anything but remote.yourdomain.com should be forwarded to the internet based DNS servers, the same as for any remote user.
I have this exact config, and it works fine.
Might you have an internal yourdomain.com forward lookup zone in place on the SBS? If so we will need to configure or remove it. (do not remove remote.yourdomain.com or what ever you use for external connections to the SBS)
ASKER
The domain name is the same internally and externally. I do not use .local
Ah, that is the problem. Microsoft discourages using the same, and it is definitely not a default SBS configuration. It causes many name resolution issues such as this.
I will see if I can replicate and resolve later today on a VM and post specific instructions. It requires configuring Split DNS.
The following outlines proper DNS configuration briefly, but it suggests an alternative to a different DNS suffix is using a sub-domain, however one of the limitations of SBS is it does not support sub/child domains, thus the importance of using .local internally.
http://support.microsoft.com/kb/254680Ah, that is the problem. Microsoft discourages using the same, and it is definitely not a default SBS configuration. It causes many name resolution issues such as this.
I will see if I can replicate and resolve later today on a VM and post specific instructions. It requires configuring Split DNS.
The following outlines proper DNS configuration briefly, but it suggests an alternative to a different DNS suffix is using a sub-domain, however one of the limitations of SBS is it does not support sub/child domains, thus the importance of using .local internally.
http://support.microsoft.com/kb/254680Ah, that is the problem. Microsoft discourages using the same, and it is definitely not a default SBS configuration. It causes many name resolution issues such as this.
Seems to work for me:
I added to the SBS DNS a forward Lookup Zone MyDomain.com which this should have replicated your configuration of having internal DNS manage the public DNS name.
I then tested my Wordpress site www.MyDomain.com and it failed as expected, because the SBS was now handling DNS for that domain (and suffix) but had no matching records.
I then added a CName record www pointing to my "real" Wordpress name, as specified in their instructions MySite.wordpress.com and it resolved and connected without issue.
Word press will only let you do so to the route of the website, not a page such as MySite.wordpress.com/home That would have to be done with a "web hop"/redirect which I know of no way of doing with internal DNS.
Keep in mind:
It needs to be a CName record, not a Host record
The alias is just www
And the FQDN target has to be your real Wordpress name MySite.wordpress.com
I added to the SBS DNS a forward Lookup Zone MyDomain.com which this should have replicated your configuration of having internal DNS manage the public DNS name.
I then tested my Wordpress site www.MyDomain.com and it failed as expected, because the SBS was now handling DNS for that domain (and suffix) but had no matching records.
I then added a CName record www pointing to my "real" Wordpress name, as specified in their instructions MySite.wordpress.com and it resolved and connected without issue.
Word press will only let you do so to the route of the website, not a page such as MySite.wordpress.com/home That would have to be done with a "web hop"/redirect which I know of no way of doing with internal DNS.
Keep in mind:
It needs to be a CName record, not a Host record
The alias is just www
And the FQDN target has to be your real Wordpress name MySite.wordpress.com
ASKER
I did create a CNAME record and it is just WWW.
I configured it to point to mydomain.wordpress.com
Here's what I think is happening:
1. I type in www.mydomain.com
2. Request gets redirected to "mydomain.wordpress.com"
3. Request reaches the Wordpress website and that gets redirected again to "www.mydomain.com" because that's configured as My Primary domain on Wordpress.
4. Wordpress strips out the WWW
5. My browser now shows MYDOMAIN.COM in the address bar
6. My PC on the internal network knows that "mydomain.com" is found locally and doesn't know that it should go out to the Wordpress servers.
I looked in the Domains section on Wordpress and there are two things configured in there:
Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress
I configured it to point to mydomain.wordpress.com
Here's what I think is happening:
1. I type in www.mydomain.com
2. Request gets redirected to "mydomain.wordpress.com"
3. Request reaches the Wordpress website and that gets redirected again to "www.mydomain.com" because that's configured as My Primary domain on Wordpress.
4. Wordpress strips out the WWW
5. My browser now shows MYDOMAIN.COM in the address bar
6. My PC on the internal network knows that "mydomain.com" is found locally and doesn't know that it should go out to the Wordpress servers.
I looked in the Domains section on Wordpress and there are two things configured in there:
Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress
@robwill http://support.microsoft.com/kb/254680Ah page has moved
Thanks ve3ofa. Seems I sort of messed up that post by duplicating later part and not having a space after the URL. Correct URL is:
http://support.microsoft.com/kb/254680
http://support.microsoft.com/kb/254680
>>"I looked in the Domains section on Wordpress and there are two things configured in there:
Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress"
I suspect the issue is you should have:
www.Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress"
This is how mine is configured. Wordpress only allows redirects (aliases) to the root domain name.
Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress"
I suspect the issue is you should have:
www.Mydomain.com <-- primary domain
mydomain.wordpress.com <-- default domain that gets created by Wordpress"
This is how mine is configured. Wordpress only allows redirects (aliases) to the root domain name.
ASKER
Not quite sure how to change this to just say "WWW.MYDOMAIN.COM" because it currently just says "MYDOMAIN.COM" and then I created A records that are needed for other purposes. (i.e. remoting in and email).
Who manages public DNS, Wordpress or a 3rd party registrar?
Normally you just change the wordpress site from mydomain.com to www.mydomain.com and the registrar holds your various A records and a CName record pointing www.mydomain to mywordpresssite.mydomain.c
The registrar may also have a default "*" record that points mydomain.com to www.mydomain.com but to the best of my knowledge SBS will never be able to resolve mydomain.com to anything external where you use the same domain suffix internally and externally.
By the way you cannot change the Domain suffix on any SBS without completely rebuilding the server and domain from scratch.
Normally you just change the wordpress site from mydomain.com to www.mydomain.com and the registrar holds your various A records and a CName record pointing www.mydomain to mywordpresssite.mydomain.c
The registrar may also have a default "*" record that points mydomain.com to www.mydomain.com but to the best of my knowledge SBS will never be able to resolve mydomain.com to anything external where you use the same domain suffix internally and externally.
By the way you cannot change the Domain suffix on any SBS without completely rebuilding the server and domain from scratch.
ASKER
Wordpress manages public DNS. I had to do it this way to get the WWW record to work right because Wordpress will not map the "www" subdomain unless you use their DNS servers.
I do believe there's a default "*" record that points mydomain.com to www.mydomain.com. In other words, I type in "www.mydomain.com" but Wordpress strips the www and only shows "mydomain.com" in the address bar.
So what you're saying is to have Network Solutions manage the DNS records and then create a CNAME record that points www.mydomain.com to "something.wordpress.com" ??
I do believe there's a default "*" record that points mydomain.com to www.mydomain.com. In other words, I type in "www.mydomain.com" but Wordpress strips the www and only shows "mydomain.com" in the address bar.
So what you're saying is to have Network Solutions manage the DNS records and then create a CNAME record that points www.mydomain.com to "something.wordpress.com" ??
I see your dilemma. Where Wordpress is hosting your DNS and they will not map www, which of course is complicated by your LAN using the same domain suffix.
Currently I have a 3rd party managing DNS (DynDNS.com) and Wordpress is set up to host/map a sub-domain blog.lan-tech.ca
To deal with www I have a redirect with DynDNS that points www.lan-tech.ca to blog.lan-tech.ca/home
I was not aware until now that they will not allow www to be used as a subdomain.
Your primary problem is having the internal domain suffix the same as the public, but that cannot be changed.
Currently I have a 3rd party managing DNS (DynDNS.com) and Wordpress is set up to host/map a sub-domain blog.lan-tech.ca
To deal with www I have a redirect with DynDNS that points www.lan-tech.ca to blog.lan-tech.ca/home
I was not aware until now that they will not allow www to be used as a subdomain.
Your primary problem is having the internal domain suffix the same as the public, but that cannot be changed.
ASKER
Sorry for the delayed response, I've been out sick for the last few days.
I decided to just use the website http://domain.wordpress.com so I moved the public DNS hosting back to Network Solutions. I then created a CNAME record for "www.domain.com" and the redirection is working ok from the outside.
I created the same CNAME record on the inside but it's not redirecting correctly. Somehow it still points to the local server instead of redirecting to http://domain.wordpress.com
I've tried to flush the DNS cache, reboot the server but it's still not redirecting.
What do you suggest I do?
I decided to just use the website http://domain.wordpress.com so I moved the public DNS hosting back to Network Solutions. I then created a CNAME record for "www.domain.com" and the redirection is working ok from the outside.
I created the same CNAME record on the inside but it's not redirecting correctly. Somehow it still points to the local server instead of redirecting to http://domain.wordpress.com
I've tried to flush the DNS cache, reboot the server but it's still not redirecting.
What do you suggest I do?
The cname record should point www to domain.wordpress.com without the http:// and clear your browser's cache as well as flushing DNS and see if it works. It should.
ASKER
Yes, I tried that. Still not working.
Very odd I was able to successfully duplicate on two virtual machines, however there was a difference, though I doubt it would make a difference.
Cname records:
blog => WPdomain.wordpress.com
www => WPdomain.wordpress.com\hom
Just due to blog having been set up long before www.
Cname records:
blog => WPdomain.wordpress.com
www => WPdomain.wordpress.com\hom
Just due to blog having been set up long before www.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry to hear you were not able to resolve.
--Rob
--Rob
ASKER
I gave up on trying to get this to work properly. I may have to host the Wordpress website myself or just have people go directly to the URL when they're at the office.
http://en.support.wordpress.com/domains/map-existing-domain/