Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

UPDATE 1:

Basically, from a computer outside the network, I can access the website by typing into the browser address bar, either of the following, which is how it should be:

http://www.companyname.com
http://companyname.com

However, from within the company network, we can only access the external website by typing in

http://www.companyname.com

It will not work if I type

http://companyname.com

ORIGINAL QUESITON:

Our internal network has the same domain name as our external website, lets say it's companyname.com for both the website and for our internal network.

This is causing problems because I am unable to access the companyname.com website from within the network. I have to use a computer from outside the network to see the website.

Is there a way around this issue, ideally without having to change the internal or external domain names?

share|improve this question
    
look at my explanation in my answer. That's what's happening. –  Holocryptic Apr 6 '11 at 9:36

4 Answers 4

up vote 3 down vote accepted

You need a split DNS

http://www.isaserver.org/tutorials/You_Need_to_Create_a_Split_DNS.html

A hacky way to fix it would be to put an A record in your DNS that points to the IP of the website. (So www.yourcompanyname.com resolves to the website address)

The best way to fix it would be a split DNS. And that about sums up my knowledge of it. You might get lucky and have someone else expound further on it.

What you're seeing is (based on my experience) *.yourcompanyname.com resolving to the SOA in DNS, which is why you're not able to get to the website internally. Put in an explicit A record for www and that should fix it.

share|improve this answer
    
Where does this new A record go? In our internal DNS server, or the external DNS server? –  oshirowanen Apr 6 '11 at 9:39
    
You're having the problem internally, so your internal DNS. –  Holocryptic Apr 6 '11 at 10:33
    
I should also say that you're not going to be able to do anything else but what you have already. If you can resolve it internally by going to www.yourcompanyname.com that's about the best you can hope for with your current situation. –  Holocryptic Apr 6 '11 at 10:35
    
Even with the split dns solution? –  oshirowanen Apr 6 '11 at 10:48
    
well, no that would fix it. sorry, I meant that comment to regard the A record fix. –  Holocryptic Apr 6 '11 at 11:16

Your terminology is little confused, so your description of the problem is not detailed enough to suggest a solution. And, in fact, if you clear up your wording, you may discover that a solution will then suggest itself to you.

Networks don't have domain names. Do you mean that a resource on your internal network has the same domain name as your website. And do you mean that it has a different host name within the same domain, maybe www.companyname.com for the website and intranet.companyname.com for the internal resource, or are they the exact same host name? Finally, do you need to be able to access both the internal and external resources at the same time from the same computer?

share|improve this answer
    
Really sorry about that. I don't know anything about networking, I am a programmer, trying to make my life a little easier. –  oshirowanen Apr 6 '11 at 9:56

When referring to your external website as companyname.com, do you actually mean www.companyname.com?

If so, the solution is simple. Just create an A record in your DNS that points to the external IP address for your website.

If you are referencing your external website by companyname.com, then you can't redirect that name internally, as that DNS entry is required to point where it currently does for your AD to function. You only option is to change your web site to use www.companyname.com.

This is one of the very reasons why I always use companyname.local internally, and companyname.com externally.

share|improve this answer
    
Please see update 1 in the original question. –  oshirowanen Apr 6 '11 at 9:36

In your description of the problem you have not indicated if this is as Windows or Linux environment, if its Windows than in your DNS server you can add a new Host A record using your websites Public IP address.

Edit - Brians answer

share|improve this answer
    
The tags specify Windows –  Bryan Apr 6 '11 at 9:32
    
Yes, our internal network in Windows based, and our external website is Linux based. –  oshirowanen Apr 6 '11 at 9:57

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.