I'm a idiot, but......
why not have the webservers on the domain controller just point to the
www.mycompany.com?
Its a patch but it would be one quickly deployed one.
Just set the delay in the meta tag to = 0 and most users won't even
know they got bounced to another page.
okay let the flaming start.
On Aug 26, 10:24 am, Brandon Tice <
brandont...@gmail.com> wrote:
> My question is this:
>
> Let's say I own a company called MYCOMPANY and I own the web site
>
mycompany.com which can be reached externally by going tohttp://www.mycompany.comORhttp://
mycompany.com. All that is great.
>
> However, from within our internal Windows network, you can only access our
> site by going tohttp://
www.mycompany.com. If you attempt to go tohttp://
mycompany.com, you get an "Under Construction" message. Now I
> believe that is because when you attempt to go tohttp://
mycompany.com, you
> aren't actually hitting the webserver, but rather the Active Directory
> domain controller. When I run an nslookup
onwww.mycompany.com, I get a
> result of the internal IP address of the webserver, which is correct.
> However, when I run an nslookup on
mycompany.com with no WWW, then I get a
> list of all of the domain controllers in the company instead of the
> webserver, which is not in the list at all.
>
> So basically the problem is that our Active Directory domain that we all log
> into is MYCOMPANY and the web address is
mycompany.com, which internal DNS
> resolves to the domain controllers rather than the webserver. I realize
> that thehttp://www.mycompany.comsite works internally due to the A record