|
Home > Archive > 70-216 > January 2003 > Exclusive mode
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| me? I dunno... 2003-01-02, 8:33 pm |
| Exclusive mode on a forwarding server is basically the same idea as iterative query? | |
| me? I dunno... 2003-01-02, 10:51 pm |
| So if I had win98 clients on a mixed mode Win2k Active Directory domain, then I would set up a standard secondary server for the legacy clients, as opposed to a standard primary server? | |
| jeff_j_black 2003-01-03, 9:14 am |
| Your clients will be able to use either Primary or Secondary zones to resolve names. Secondary zones are just read-only copies of their master.
I'm not really familiar with the term Exclusive Mode, what is the context?
Happy New Year!!! | |
| me? I dunno... 2003-01-03, 2:51 pm |
| From 'Examprep' Windows 2000 active directory services text,
"Forwarding servers can be configured to use either nonexclusive or exclusive mode. In nonexclusive mode, a name server can attempt to resolve a query through its own zone database files if a forwarder cannot resolve the query. In exlclusive mode, if a forwarder cannot resolve a query, the server that sent the query to the forwarder does not attempt to resolve the name itself, and simply returns a failure notice to the client that originated the request."
I'm trying to remember this as similar to recursive/iterative for mnemonic purposes while gearing back up for another go at 217
Also, re the primary, secondary thing, I was wondering about the primary server needing to be the only one in the zone. If dns primary server is a member server in an AD domain, then there would still be replication via AD. Does that not then cause any conflicts with a primary server for a standard primary zone within an AD zone?
and Happy New Year to you and yours also! Hopefully it will be one of improved sanity in the world. | |
| jeff_j_black 2003-01-03, 3:25 pm |
| quote:
In nonexclusive mode, a name server can attempt to resolve a query through its own zone database files if a forwarder cannot resolve the query.
Would be Recursive
quote:
In exlclusive mode, if a forwarder cannot resolve a query, the server that sent the query to the forwarder does not attempt to resolve the name itself, and simply returns a failure notice to the client that originated the request.
Would be Iterative.
quote:
Also, re the primary, secondary thing, I was wondering about the primary server needing to be the only one in the zone. If dns primary server is a member server in an AD domain, then there would still be replication via AD.
Remember: only Active Directory Integrated zones are replicated along with AD. Primary zones can replicate with designated Secondary zones. Active Directory Integrated zones can only be hosted on a Domain Controller, hence the replication along with AD. But there could be Secondary zones that are copies of the AD Integrated zone.
You can have several zones on the same network: 1 or more Active Directory Integrated, A Primary zone with Secondaries, Caching Only zones etc. | |
| me? I dunno... 2003-01-03, 5:01 pm |
| quote:
You can have several zones on the same network: 1 or more Active Directory Integrated, A Primary zone with Secondaries, Caching Only zones etc.
so then, any or all of these zones can overlap with impunity as long as each client has the appropriate dns server, that it wants to use, address entered in its nic card properties box?
can a standard primary or standard secondary be included in an AD integrated dns servers zone transfer list? Is that how to keep legacy client segments up to date? | |
| jeff_j_black 2003-01-04, 9:04 am |
| I don't think it would be wise to overlap zones. But for example:
Where I work, we are going to have a zone for the internet that uses forwarders to resolve external addresses, a zone for addresses that we want to expose to the public, a zone for internal fixed resources whose records won't change frequently and will require little maintenance. All of the above zones will be Primary zones with Secondary zones.
Finally we will have our internal zone for clients, services and resources, etc. and it will be AD integrated.
So to the point of your question: You could have AD Integrated zones with Secondaries of that zone or a Primary zone with Secondaries. AD integrated is a multi-master affair, each server is able to update records. In a Primary zone there is only one Primary writable database and any replicas you wish to have on Secondaries are read only.
Both AD Integrated and Primary zones can be transferred to designated Secondary zones.
When you make a zone either Primary or AD Integrated, you are saying to the network that this zone is authoritative for this namespace, hence you would not want to cover the same real estate with both a Primary and AD Integrated zones as they can not replicate between them. | |
| me? I dunno... 2003-01-05, 3:01 am |
| Thank You |
|
|
|
|