D
Dave Woolley
Hello,
I've got a Windows 2000 AD network "domain.com" utilizing internal DNS
servers. Our external website utilizes the same domain ("domain.com")
and is hosted by someone else. To allow internal hosts to resolve
I've added an A record which points www to the external website.
Everything works fine with that, though it is a little slow in
resolving.
Recently a new section was added to our external site... ie.
http://www.domain.com/groups. This resolves fine externally but
produces a "page not found" on the internal network. Other sections
of the site resolve fine... ie. http://www.domain.com/sponsorship.
The only thing I can think of that may be affecting resolution of
/groups is that we have a share of the same name on one of our Windows
2000 domain controllers.
Does anyone have any thoughts on what may be causing this issue and
how to resolve it?
Thanks in advance for your help!
-Dave
I've got a Windows 2000 AD network "domain.com" utilizing internal DNS
servers. Our external website utilizes the same domain ("domain.com")
and is hosted by someone else. To allow internal hosts to resolve
I've added an A record which points www to the external website.
Everything works fine with that, though it is a little slow in
resolving.
Recently a new section was added to our external site... ie.
http://www.domain.com/groups. This resolves fine externally but
produces a "page not found" on the internal network. Other sections
of the site resolve fine... ie. http://www.domain.com/sponsorship.
The only thing I can think of that may be affecting resolution of
/groups is that we have a share of the same name on one of our Windows
2000 domain controllers.
Does anyone have any thoughts on what may be causing this issue and
how to resolve it?
Thanks in advance for your help!
-Dave