We help IT Professionals succeed at work.

Cannot access website from the LAN

daskas27
daskas27 asked
on
Hello,
       I submitted this question a while ago and received some good answers. I have used the same title so the experts can easily search for it for reference. I have finally got around to getting this done and find that I have additional questions. I was hoping that I could get an example of a host file before I attempt to apply the solutions given to me earlier. Here is the original question:

       We recently installed a new server at our location. It is Windows Server2012. It is an AD environment. When we installed this server we chose to use our registered domain as the domain that this server would control. We now can no longer access our company website from the lan which is hosted at godaddy. I think I know the problem, ( computers on the lan are going to the server when they try to go to external website). I just don’t know how to fix it. Any help with this would be appreciated.

 Thank you
Comment
Watch Question

MaheshArchitect
Distinguished Expert 2019

Commented:
not sure if i understood your question

When we installed this server we chose to use our registered domain as the domain that this server would control

Can you elaborate more what exactly you have done ?
daskas27IT manager

Author

Commented:
Our website is hosted at godaddy. Lets call it www.dave.com. The new server's domain is dave.com. If I try to get to the website dave.com it goes to the server and comes back with unable to display page. If I go to a proxy like megaproxy.om I can there. This tells me that the server does not know to tell the request to go to the hosted site. Here is the link to the original question:

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_28522889.html

Thank you,
Dave
MaheshArchitect
Distinguished Expert 2019

Commented:
Ok
have you created dns zone named dave.com on this dns server and does it points to public IP of web site?

Also what dns your clients are pointing for name resolution?

If client are domain joined, you should create dave.com zone on domain controller DNS
daskas27IT manager

Author

Commented:
Yes, that is my question. How do I do that?

Thank you
Principal Support Engineer
Commented:
Yes, that is my question. How do I do that?
You can't really do that in this case. There's already going to be a forward lookup zone named dave.com on your internal DNS server (the domain controller) because your AD domain is named dave.com. Inside that zone, there will be one or more "blank" host records whose names will show up as (same as parent folder) in the DNS console, and the IP addresses of those records will correspond with the IP addresses of your domain controllers. This is how it has to be in AD, and this arrangement shouldn't be tinkered with.

One result of this is that if a machine in your domain tries to resolve the name dave.com, that name will be resolved to a domain controller in the domain. That is by design. For this reason, the simplest way to work around this issue is to make sure the website is configured to respond to www.dave.com instead of simply dave.com. This may involve removing an HTTP redirect, creating a host header, and/or modifying internal links in the site code. You will likely have to have a conversation with the web host and/or designer who created the site in order to accomplish this.

Once that's done, create a host record named www on your internal DNS server and give that record the IP address of the website. Your internal users (possibly after flushing the resolver caches on their machines) should then be able to access the site using the name www.dave.com. There won't be a way for them to browse to the site using the name dave.com, though; that's just not going to happen.

There is another possible solution, but I don't like it: install IIS on your domain controller, configure the default web site to respond to the name dave.com, and redirect requests for that site to the web site's public IP address. This will allow your internal users to browse to the site using dave.com, but I don't like this solution because I'm not a fan of installing IIS (or any other extraneous services) on a domain controller. And note that if you add more domain controllers in the future, you'll have to do the same thing on all of them.
MaheshArchitect
Distinguished Expert 2019

Commented:
Assuming you have AD environment, You should create AD integrated dns zone named dave.com on DC and create required record in that zone to resolve to public IPs

Now your clients should point to AD DNS, they should get server hosted in Go Daddy
MaheshArchitect
Distinguished Expert 2019

Commented:
@author:
I think you have split dns scenario

DrDave242 correctly explained situation
daskas27IT manager

Author

Commented:
"Once that's done, create a host record named www on your internal DNS server and give that record the IP address of the website."
This is the item I was hoping to get an example of.
DrDave242Principal Support Engineer

Commented:
Open the DNS console on the domain controller and select the dave.com forward lookup zone in the left pane. In the right pane, right-click empty space inside the zone and select New Host (A or AAAA). In the New Host dialog, specify www for the name of the record, and supply the website's public IP address in the IP address field. Click Add Host, and the record will be created.
daskas27IT manager

Author

Commented:
Thank you. I will have to wait until morning to get to this. I will report my results. Thanks again.
daskas27IT manager

Author

Commented:
Thank you