I'm a little rusty with my Microsoft stuff, but I believe that the real requirment you're looking for is a Dynamic DNS server. I specifically recall this need from my Windows 2000 server manuals. The windows DNS server offers this capability (which is why they want you to use theirs). I'm not a DNS guru and I would like to know what Linux/Unix based solutions offer this feature in a DNS server. James > Okay, please don't rip my head off here for asking a MS question, but I > figured I would get a slightly less biased answer here. That being > said.... > We are upgrading our Exchange 5.5 server to Exchange 2003. We are a > mixed shop with Linux and Windows. (There are numerous other systems, > mostly of the *nix variety) While I tried to edge them to use > Communitgate Pro, Contact, or OpenExchange, they decided there would be > less impact on users if we stayed with Exchange. > Now comes my issues, I feel like Alice falling down the rabbit hole > here. In reading the docs for Exchange 2003, it says it needs Active > Directory. Great, so now I have to learn Active Directory and futz with > that. Now I am setting up Active Directory, flying by the seat of my > pants, and it says that it wants its own DNS server in order to work > properly. All my DNS servers are Linux based. > Can Active Directory work with Linux based DNS? I thought I recalled a > few of you saying you had Exchange 2000/2003 running, just wanted to > know how you did it. > Any help would be appreciated. > > -- > Edward M. Croft > Sr. Systems Engineer > Open Ratings, Inc. > 200 West Street > Waltham, MA 02451-1121 > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
