|
That is pretty much how we have it set
right now…BIND for public facing DNS, which causes no problems. But, the
internal DNS servers still need to point domain.edu to the web server, as those
are the DNS servers that everyone on campus actually points to. How do I get
around them possibly resolving the wrong IP when going to domain.edu in a browser?
As it stands now, there is a possibility they will resolve to the IP of a DC. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Hi Doug, The situation you're describing is called split DNS, and is rather
common. What you have in this scenario is two sets of DNS servers - internal
(AD), and external (public facing). Your public facing DNS servers have things
like the Internet Ip of your WWW and your MX records and good stuff like that.
There's no sign of the AD DNS in your public facing DNS. Internally, you duplicate all the necessary records on the AD DNS as
they are in teh external zone, except you may wish to use the private IPs
instead if you want. Does this help? --Brian
|
Title: [ActiveDir] Kinda OT: DNS entry
- [ActiveDir] Kinda OT: DNS entry Doug M. Long
- RE: [ActiveDir] Kinda OT: DNS entry Brian Desmond
- RE: [ActiveDir] Kinda OT: DNS entry Doug M. Long
- RE: [ActiveDir] Kinda OT: DNS entry deji
- RE: [ActiveDir] Kinda OT: DNS entry Brian Desmond
- RE: [ActiveDir] Kinda OT: DNS entry Doug M. Long
- RE: [ActiveDir] Kinda OT: DNS entry deji
- RE: [ActiveDir] Kinda OT: DNS entry Doug M. Long
- RE: [ActiveDir] Kinda OT: DNS entry Frost . David
