Just in case, but do you understand stub zones aren't the
same thing as secondary zones? If you had 2003 you could use either stub
zones or conditional forwarding and achieve the same effect. Stub zones
are just a little easier to AD integrate (since it's exposed in the GUI) and you
can have it dynamically maintain the list of NS records.
To your other question, no you can't upgrade DNS to 2003
and leave the OS at 2000. It's all or nothing.
The secondary zone scenario is if you remain at 2000.
You create the secondary zones on your 2000 DNS servers with the Linux server
designated as the primary.
David as you see i am learning process :)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Milton Sancho
Sent: Thursday, March 30, 2006 11:26 PM
To: [email protected]
Subject: Re: [ActiveDir] Selectively overriding hierarchical lookup
Definitely I need to configure conditional forwarders instead of stub zones! Then I have two DNS Server running on a Win 2000 (2 DC's) environment; may I upgrade those DNS Servers to 2003 altough those are running in windows 2000 server ?
Host a secondary copy of the zone ? well, I do not need to create zones on this scenario... right
On 3/30/06, David Adner <[EMAIL PROTECTED]> wrote:Host a secondary copy of the zone on the 2000 server. Or upgrade it to 2003. :)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Milton SanchoSent: Thursday, March 30, 2006 9:49 PMSubject: Re: [ActiveDir] Selectively overriding hierarchical lookupWhat would happen if am running MS DNS on Win Server 2000 ?
We create recently a corporate domain on win 2003 enviroment, but our production domain is running on win 2000 , all client computers are pointing to the production domain... mainly we need to find a way to do the process you explained on a MS DNS 2000
Thanks comments
On 3/30/06, David Adner <[EMAIL PROTECTED]> wrote:Assuming I understood you correctly, if your MS DNS server is running on Windows Server 2003 then you could leverage stub zones or conditional forwarders. With either method you could, for example, say any queries for "linux.com" (or whatever it's called) go to your Linux DNS server while all other queries that cannot be resolved locally are sent to forwarders/root hints.
From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Milton Sancho
Sent: Thursday, March 30, 2006 8:41 PM
To: [email protected]
Subject: [ActiveDir] Selectively overriding hierarchical lookupHow can one override a recursive lookup for a domain not hosted on a Microsoft DNS Server?
The scenario is a local network with a Microsoft DNS Server running both as an authoritative server for some local domains and as a DNS solver for all the internal clients.
So far, so good.
- For reasons outside the scope of this query, a separate authoritative server (djbdns on linux) was set up for certain domains belonging to the company.
This server has a private IP where the domains are being published for internal use, and it would be preferable for the Microsoft DNS Server to query this server directly for all these domains, rather than resolving hierarchically down from a root server.
- The local linux guys say this can be done easily on djbdns, just telling the cache the ips of the servers which all queries related to a domain should be directed to.
The question is: How can you tell a Microsoft DNS Server which servers to query for a certain domain, thus selectively bypassing the usual TLD-SLD-LD lookup?
Thanks comments
