R
Rich Hancuff
I have a strange problem:
I work in a school at a university and we have a Windows
2000 domain running specifically for our school. As such
it runs DNS, but only for domain purposes; the university
runs the external DNS servers. That means any of our
machines that offer webservices have an entry in the
external dns zone.
1. In our domain, apple.banana.edu, we have a DC running
DNS with ADI zones.
2. Our webserver is in house, and its FQDN in the AD is
webber.apple.banana.edu, but the registered name for
users accessing the website is www.banana.edu
3. If we set our domain computers to use the DC as the
primary DNS server instead of allowing the university's
DNS server to be primary, we cannot access our website
www.banana.edu from those computers: it goes into a
constant refresh.
Has anyone seen this before and if so how do we resolve
it?
Thanks
Rich Hancuff
I work in a school at a university and we have a Windows
2000 domain running specifically for our school. As such
it runs DNS, but only for domain purposes; the university
runs the external DNS servers. That means any of our
machines that offer webservices have an entry in the
external dns zone.
1. In our domain, apple.banana.edu, we have a DC running
DNS with ADI zones.
2. Our webserver is in house, and its FQDN in the AD is
webber.apple.banana.edu, but the registered name for
users accessing the website is www.banana.edu
3. If we set our domain computers to use the DC as the
primary DNS server instead of allowing the university's
DNS server to be primary, we cannot access our website
www.banana.edu from those computers: it goes into a
constant refresh.
Has anyone seen this before and if so how do we resolve
it?
Thanks
Rich Hancuff