Primary DNS causes Web Page to Refresh constantly

  • Thread starter Thread starter Rich Hancuff
  • Start date Start date
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
 
In
Rich Hancuff said:
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

If I'm getting the picture right, create a forward lookup zone on the Win2k
DNS named www.banana.edu then create a new host leave the name field blank,
and give it the IP of the internal Web server. This way all other queries
except www.banana.edu and names in apple.banana.edu will be forwarded.
 
Thank you very much. It worked like a charm. I have much
to learn about this DNS.
Rich
 
Please explain why this solution was used instead of forwarding or
delegation?

Lee
 
In
Leon E. Webster said:
Please explain why this solution was used instead of
forwarding or delegation?

Because www.banana.com was the only name that needed to resolve to a
different IP than was in the public DNS, this site was local with a local
IP.
 
Back
Top