Our network name happens to be the same as our website name.
The web site was in our DMZ. To provide access, I added www to the dns which then appended our domain and top domain to it. The IP was the IP in our DNS.
We just moved our website to a hosting facility and it no longer has a unique IP address so the old work-around doesn’t work.
Any suggestions on how to address the web site from within our network?
We just moved our website to a hosting facility and it no longer has a unique IP address so the old work-around doesn’t work.
Any suggestions on how to address the web site from within our network?
Who is Participating?
You will have to change the zone record for that domain so that it points at the IP address of the server where the site is hosted. Your network name should be a .local address and not the .com address.
Unfortunately those hosting the site use dynamic ip's. The local domain being the same as the website was a poor design and yes I could change the local to local(domainname).com. I am having those now in control of the NS for the site create a subdomain and I will create a cname in dns to point to that subdomain which they will then point at mywebsite.com.
Having the same spelling between the AD Domain and the Public Domain is perfectly fine as is preferred. The option of ".local" is pushed by the common Small Business Server installation process and other popular articles, but is a bad idea in general. One, the TLD should be three letters or less for improved universal compatibility, and Two, using the spelling of the Name that you actually own assures that there is no way that anyone out in Internet Land won't suddenly buy a Public Domain Name spelled the same your internal Domain Name.
Contrary to popular belief,..".local" is not an officially reserved TLD,...there are only 3 or 4 of those and ".local" is not one of them. Not taking this seriously,..and ending up in a situation where someone else on the Internet buys a Public Domain Spelled the same your your Internal AD Domain makes buying Certificates, which are required to be matched to your AD Domain Name, will become impossible becuase no two entities can officially use the same Domain,..and the other people who bought it would have the rights to it.
As far as the Hosting company,...you have to do whatever it takes to get them to use an Address that does not change,...it can remain DHCP,...but it has to be Reserved so that it does not change. Having the IP of a Public Web Site randomly changing is just totally unacceptable and that has to be fixed,...it is as simple as that.
Contrary to popular belief,..".local" is not an officially reserved TLD,...there are only 3 or 4 of those and ".local" is not one of them. Not taking this seriously,..and ending up in a situation where someone else on the Internet buys a Public Domain Spelled the same your your Internal AD Domain makes buying Certificates, which are required to be matched to your AD Domain Name, will become impossible becuase no two entities can officially use the same Domain,..and the other people who bought it would have the rights to it.
As far as the Hosting company,...you have to do whatever it takes to get them to use an Address that does not change,...it can remain DHCP,...but it has to be Reserved so that it does not change. Having the IP of a Public Web Site randomly changing is just totally unacceptable and that has to be fixed,...it is as simple as that.
While checking the site from outside the network I realized the host had the site resolving to mydomain.com and not www.mydomain.com. With that minor change on their end all is well. Thank you for all your information it was very helpful as always.
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.
All Courses
From novice to tech pro — start learning today.
.test
.example
.invalid
.localhost
Here are the only real reserved Second Level Domains (SLDs)
example.com
example.net
example.org
Here is the documentation (RFC2606):
http://tools.ietf.org/rfc/rfc2606.txt