?
Yeah, I think you previous post pretty much said it all. I would break my own knee if 
I install IIS on one of the DCs. Thanks for the responses

________________________________

From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED]
Sent: Mon 8/9/2004 6:48 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Kinda OT: DNS entry



Doug, read my previous response to you. Don't set that mydomain.edu A record
to point to your webserver. You will do more harm to your AD infrastructure.
That A record belong to your DCs.


Sincerely,

D説 Ak󭶬ᦩ, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday?  -anon

________________________________

From: [EMAIL PROTECTED] on behalf of Doug M. Long
Sent: Mon 8/9/2004 3:11 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Kinda OT: DNS entry


?
OK, I will try to explain a little better with an example.
Active directory domain = mydomain.edu

Domain controller A =  a.mydomain.edu = 192.168.1.5 hence mydomain.edu
resolves to this
Domain controller B =  b.mydomain.edu = 192.168.1.7 hence mydomain.edu also
resolves to this
webserver = mydomain.edu = 192.168.1.9

If only webserver read srv records.

(internal) If I open a web browser and put http://mydomain.edu <http://mydomain.edu/>  
it will
actually go to the webserver about 1/3 of the time. I do a ping on domain.edu
and it returns one of three different IPs (not always the same IP). Now, if I
put http://www.mydomain.edu <http://www.mydomain.edu/>  it works fine everytime, 
because I only have one
IP resolving to that name.

I am thinking now that what I am trying to do is not actually possible, but
want to make sure.



________________________________

From: [EMAIL PROTECTED] on behalf of Brian Desmond
Sent: Mon 8/9/2004 5:41 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Kinda OT: DNS entry


I'm not sure i understand. What problem is the webserver having? If it has a
public IP, create the A record in internal record with the proper IP...

--Brian

        -----Original Message-----
        From: Doug M. Long [mailto:[EMAIL PROTECTED]
        Sent: Mon 8/9/2004 12:07 PM
        To: [EMAIL PROTECTED]
        Cc:
        Subject: RE: [ActiveDir] Kinda OT: DNS entry
       
       

        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
        Sent: Monday, August 09, 2004 12:18 PM
        To: [EMAIL PROTECTED]
        Subject: RE: [ActiveDir] Kinda OT: DNS entry

        

        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

                -----Original Message-----
                From: Doug M. Long [mailto:[EMAIL PROTECTED]
                Sent: Mon 8/9/2004 9:45 AM
                To: [EMAIL PROTECTED]
                Cc:
                Subject: [ActiveDir] Kinda OT: DNS entry

                What is the proper way to DNS my domain so that people are
pointed to
                the web server? Currently I have www.domain.edu DNSed to the
web server
                (where domain.edu is our Active Directory domain). I would
also like to
                DNS domain.edu to the web server. Will I run into issues with
this? When
                I DNSed domain.edu to our pop3 server (don't ask why) we were
having
                problems with the mail  clients not using the correct DNS
entry (because
                domain.edu was DNSed to two DCs and a front-end pop3 server).
               
                Oh yeah, I am using AD integrated DNS (if that matters).
               
                Any help is appreciated.
               
                List info   : http://www.activedir.org/mail_list.htm
                List FAQ    : http://www.activedir.org/list_faq.htm
                List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/



<<winmail.dat>>

Reply via email to