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

For some reason, we are blocked from accessing our external website from within our company network.

For example. from the company network, only http://www.companyname.com works, but http://companyname.com does not work.

If I try http://www.companyname.com and http://companyname.com from home, both work properly.

share|improve this question
    
What IP does companyname.com resolve to within your company network and is it different to www.companyname.com? –  Ethos Feb 21 '11 at 11:08
    
I don't know the answer to the first question, but the answer to the second question is that it is definitely different from www.companyname.com. –  oshirowanen Feb 21 '11 at 11:43

2 Answers 2

up vote 2 down vote accepted

You should talk to your system administrator about this as it sounds like your company is using split DNS and the internal DNS doesn't have a record for companyname.com.

share|improve this answer
    
Thanks, will speak to sys admin. –  oshirowanen Feb 21 '11 at 11:42
    
The sys admin has added a 'www' A record to the companyname.com zone, and it makes no difference. –  oshirowanen Feb 21 '11 at 14:10
    
@oshirowanen, as www was already working the admin needs to add the appropriate record for letting you get to the site without needing www. –  John Gardeniers Feb 21 '11 at 19:03

It sounds like your active directory domain may also be companyname.com, if not then it sounds like your internal DNS server does not have the correct records for it.

Add a new A record for company.com on your internal DNS server pointing to your external website. If company.com is your internal domain name then I would not recommend doing this. You might look at creating a new internal only record for this, something like http://website/ which does a redirect to www.companyname.com. Not ideal but the only solution I can think of.

share|improve this answer
    
I think you might be right. We are using company.com for our active directory domain. –  oshirowanen Feb 21 '11 at 11:41
    
in that instance company.com should always resolve to one of your domain controllers. –  pablo Feb 21 '11 at 13:15
    
I don't understand? When I type companyname.com. I get a host refused connection error message in the browser, even though it works from my phone which is not using the network I am trying to access it from. –  oshirowanen Feb 21 '11 at 14:09
    
from a command prompt type nslookup companyname.com. It will likely return the ip of your domain controller, rather than your website. Active Directory doesn't know its a website, it just knows that its your internal domain name. –  pablo Feb 21 '11 at 15:55

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.