Windows Internal website not resolving

Hello,
 i have an external a record pointing to name.companyname.net pointing to my static ip provided by verizon. this works fine when people go to the website companyname.net which is hosted on network solutions, then click a link for name.companyname.net/name it goes to our sbs 2008 server to an internal database/web application. all is well externally. internally i can not put in name.companyname.net/name in a browser and it will work. if i use the serveripaddress/name than it works fine. anyone have a tip as to how to fix this? thank you
jsgouldAsked:
Who is Participating?
 
Andrew DavisManagerCommented:
Mutawadi,
     I dont believe that will work.

The question as asked is a bit confusing. but what i think is happening is:-
you have a site www.yourcompany.net hosted externally, and an Public DNS A record that points to the external providers IP address.
then you have an internal App (lets use Outlook web access as an example) hosted internally at mail.yourcompany.net/owa and you have a DNS A record for "mail" pointing to your static ip address, which i assume is going to your router and then peing port forwarded to the server.

This would work fine externally but would fail internally because when an internal user goes to mail.yourcompany.net they will be given the External interface IP of your router, and it cannot port forward an internal back in (this is normal).

Assuming all above is correct.
You need to open DNS on your internal server and add a zone for yourcompany.net
then add the A record for www to your web site hosting IP address.
Add a second A record for mail to your servers internal IP address.

Then when your internal users request the site the DNS is provided internally so the external public DNS is bypassed.

From the answer from Mutawadi
A. Will not work as the external DNS resolution will direct the interrnal traffic to the external IP address of the router.
B. Will not work as Hosts file (and DNS) only operates on the FQDN it does not function at the subdirectory level.
    Assuming that the interl app is on a different host name ("www" vs "mail") then you could just create a hosts entry for the mail.yourcompany.net in the hosts file of each workstation, but this is messy and horrible, and means you now need to maintain all these client computers hosts records.

Cheers.
Andrew
0
 
Ayman BakrSenior ConsultantCommented:
You need to do one of the following:

1. You need to configure a forwarder on your DNS to the internet DNS containing this record
2. On the client PC where you are trying internally to access the site, update your hosts file with the record for name.companyname.net/name with the IP address of the server.
0
 
Cliff GaliherCommented:
Agreed. You need many routers will not loop back traffic from an internal address back to the internal address. The easiest fix is a split-brain DNS setup where the internal DNS server has a zone that gives a different address than the external DNS servers...hence the name split-brain.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Ram BalachandranCommented:
you can easily do this by a host file entry

http://helpdeskgeek.com/windows-7/windows-7-hosts-file/

make an entry -
<ipaddress> name.companyname.net
0
 
Andrew DavisManagerCommented:
Yes Ram,
That has been covered.
However in a network it is by no means the preferred way as you would have to manage each clients hosts file.

Also the original response of hosts file was for the sub-directory of name ( name.companyname.net/name ) which is not supported in hosts, or any domain name resolution method.

Hosts is a good way of testing operation prior to correcting the local DNS tho.

Cheers
Andrew
0
 
jsgouldAuthor Commented:
I will give it a shot Andrew as consensus points to your solution. Sorry if it was poorly worded. I was working rather late. But you where able to decipher it. I should be able to try this tonight and I will let you know the results. Thank You
0
 
Andrew DavisManagerCommented:
No problem, it should all be fine.
0
 
jsgouldAuthor Commented:
Here is what i did. created the zone for our website name "name.net" added an a record for "name.net" to point to the webhost's ip (external ip). added another a record for "www.name.net" to point to the webhost's ip  (external ip). then i added subdomain.name.net as an a record pointing to my sbs2008 server's ip address (internal ip). that fixed everything. thank you Andrew.
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.

All Courses

From novice to tech pro — start learning today.