DNS - selective replication

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have several W2K3 DCs successfully replicating (company.com) integrated DNS
entries - all private name space. Due to a quirky application, I have a need
to resolve certain host.company.com with different a IP address depending
upon which DNS/DC server is queried. Is this possible within current set up
or do I have to research an outside solution? Thanks.
 
AreJi said:
I have several W2K3 DCs successfully replicating (company.com) integrated
DNS
entries - all private name space. Due to a quirky application, I have a
need
to resolve certain host.company.com with different a IP address depending
upon which DNS/DC server is queried. Is this possible within current set
up
or do I have to research an outside solution? Thanks.
Click to expand...

Yes it is possible although it is really difficult to understand
why you would want to do such a thing -- maybe to fake a
site aware service for one that has no such concept?

On each DNS server that much have a DIFFERENT result
setup up a new ZONE with the "server name" -- note you
are using an ENTIRE ZONE to represent one server so that
it will not be part of your your overall replication.

Give that name (in that zone) an IP address (that is with no
server specific portion [same as parent] since the server
portion is already part of the zone.

Use a PRIMARY (and perhaps ordinary Secondaries) as
the type for these special zones.

You must NOT have the particular server (special.company.com)
listed in the actual parent zone (company.com).

If you wish to have several servers return the same zone/result
then you can set them up as NON-AD integrated Primary +
Secondary sets, or you can make each one a separate Primary
(these will never replicate) if you prefer.

It's ugly if you have to do this for more than a few servers times
a few results but it will work.
 
Herb Martin said:
news:[email protected]...
Click to expand...


Thanks Herb. I am seeing another interesting aspect though after I gave your
suggestion a try.

First, the reason is a web app hosted in US but used in several other
continents. To optimize performance, I need to load static contents on app
web pages locally and have dynamic data come from US. Performance boost is
30-35%. However, the app funcationality is tied to its URL which has to start
same, say: "stuckname.company.com", anywhere it's accessed from.

With this exercise, stuckname.company.com would resolve to local static
content server which will route dynamic data requests back to US hosted
facility.

Now, I am able to create "special.company.com" as a primary Non-AD zone and
assign it a different IP address on different DNS/AD hosts. However, on all
DNS/AD hosts, since "company.com" is still AD-Primay zone, an entry appears
in that zone for "special" as a sub-domain. However this entry only points to
another AD/DNS server. This entry thus causes different resolution answers.

For example, off 6 replicated DNS DCs, 3 have a diff. IP for
"special.company.com" (created as separate prim-non-AD zone) and resolve
accordingly. Other 3 do not have this Prim-non-AD zone but "special" appears
under "company.com" and depending is pointing to which AD/DNS hosts, resolves
"Special" as defined on that very host.

All in all, it works during first level tests, I will write back if I run
into some other hinderances. Thanks a ton for now.

Regards.
 
All in all, it works during first level tests, I will write back if I run
into some other hinderances. Thanks a ton for now.
Click to expand...

It would also be nice and appreciated if you update us when
and if it IS A SUCCESS.

It's nice to not only help when it fails but to get confirmation
of what (odd) methods work.
 
Back
Top