Re: [ActiveDir] Domain Name and DNS Problems

2004-12-17 Thread Rick Boza
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard, Aric Sent: Tuesday, December 14, 2004 20:01 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Domain Name and DNS Problems Edwin, You could theoretically upgrade your Exchange server to E2K3 followed by an upgrade of the OS

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-16 Thread Jorge de Almeida Pinto
] Domain Name and DNS Problems Edwin, You could theoretically upgrade your Exchange server to E2K3 followed by an upgrade of the OS to W2K3. At this point, even with the W2K Pro systems, you could perform a domain rename assuming your forest has a functional level of (2) Windows Server 2003

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-16 Thread Ricardo . Konno
Return Receipt Your RE: [ActiveDir] Domain Name and DNS Problems document

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-16 Thread Renouf, Phil
: RE: [ActiveDir] Domain Name and DNS Problems It looks like I am just going to have to deal with the DNS problem as it is. I can perform the upgrade as easy as it sounds but I have never done one before. I dont mind jumping in and doing the work but I dont think my superiors will let me. I know

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-16 Thread Edwin
: Tuesday, December 14, 2004 20:01 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Domain Name and DNS Problems Edwin, You could theoretically upgrade your Exchange server to E2K3 followed by an upgrade of the OS to W2K3. At this point, even with the W2K Pro

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-14 Thread Edwin
That is why I mentioned the Perl script that is used. That is exactly what it does. But this is not what I would like to see. I would like for our internal AD DNS to only host records for our internal systems and forward any other unresolved requests. On Tue, 2004-12-14 at 09:29 -0500,

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-14 Thread Salandra, Justin A.
Wont happen since both are the same DNS name -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Sent: Tuesday, December 14, 2004 1:01 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Domain Name and DNS Problems That is why I mentioned

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-14 Thread deji
] Subject: RE: [ActiveDir] Domain Name and DNS Problems That is why I mentioned the Perl script that is used. That is exactly what it does. But this is not what I would like to see. I would like for our internal AD DNS to only host records for our internal systems and forward any other unresolved

Re: [ActiveDir] Domain Name and DNS Problems

2004-12-14 Thread ASB
~ I would like for our internal AD DNS to only host records for our internal systems and forward any other unresolved requests. ~ Won't happen when you are using the same name both internally and externally. Your existing solution

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-14 Thread Bernard, Aric
are doing what many other organizations do when a split-brain DNS is implemented. Regards, Aric From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Sent: Tuesday, December 14, 2004 10:01 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Domain Name and DNS Problems

RE: [ActiveDir] Domain Name and DNS Problems

2004-12-13 Thread Salandra, Justin A.
Why dont you just duplicate the records in the public DNS zone to the private zone. That is what I do since both my internal and external namespaces are the same. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Sent: Tuesday, December 14,