Name Resolution--two domains

  • Thread starter Thread starter C Hall
  • Start date Start date
C

C Hall

Greetings,

I'm trying to tie up some lose ends to a network that I inherited. I have a
12 location wan, with both netware & w2k. I have the design figured out for
the most part, but there's one more problem:

A third party vendor installed a small domain, which I'll call CLUELESS, to
support their application that interfaces with our core system (as/400).
Their domain consists of 1 dc, a websever (iis) and an app server. The users
will connect to the app server through an html interface. I won't go into
all the details about how they login to our netware network along with
logging into CLUELESS, as I'm not always privy to information :-| As I'm
creating zones and configuring clients to use dns through our primary
domain, which I'll call GOTACLUE, how would I handle name resolutions for
CLUELESS? I'm thinking that I would create a secondary zone for the CLUELESS
domain on the GOTACLUE domain.

Thanks,
Chris
 
That's certainly one way of doing it, and the way I always prefer to do it.
Host a secondary copy of clueless.com on gotaclue.com and vice-versa if you
require the cluseless clients to resolve the gotaclue.com clients.

Just remember to configure the clients with both suffixes -as they're set to
append the parent by default. As of Windows XP, you can now configure this
through GPO.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/
 
Paul,

What about this: could I just add host & ptr records if the domain is on the
same subnet as one of my zones?
 
Regarding the other domain, the installers set it up as clueless.local. In
the DNS forward lookup zone there are two zones: clueless and the root "." .
The odd thing is that both are setup as AD integrated. I was intending to
setup our isp dns on the forwarders tab (all servers have our isp listed as
the secondary dns server in tcpip properties), but the option is greyed out.
Could that have something to do with the way the forward zones were created?
Any suggestions on this mess?


Thanks,
Chris
 
C Hall said:
Regarding the other domain, the installers set it up as clueless.local. In
the DNS forward lookup zone there are two zones: clueless and the root "." ..
The odd thing is that both are setup as AD integrated. I was intending to
setup our isp dns on the forwarders tab (all servers have our isp listed as
the secondary dns server in tcpip properties), but the option is greyed out.
Could that have something to do with the way the forward zones were created?
Any suggestions on this mess?
Click to expand...

Delete the "." - it's creation is a sometimes helpful
feature (or bug depending on your point of view.)

You don't need it UNLESS you are trying to provide
a common root for multiple trees of domains/zone but
that screws up forwarding to the Internet anyways.

Delete the '.' DOT zone -- the forwarder tab will be
activated (at worst a restart of the DNS service.)
 
C said:
Paul,

What about this: could I just add host & ptr records if the domain is
on the same subnet as one of my zones?
Click to expand...

If I remember, your other posts in the other thread below, you mentioned you
have Netware DNS servers. The version you have can't support the SRV records
required for AD if you are to create a secondary zone. Check the zone to
make sure they transfer on the Netware DNS (if you are to use them). Test it
with nslookup to ensure the SRVs are resolvable.

Ace
 
Ace,

Per the info learned in the previous thread, I'm canning the netware dns.

Thanks,
Chris
"Ace Fekay [MVP]"
 
Thanks, Herb.

Herb Martin said:
"."

Delete the "." - it's creation is a sometimes helpful
feature (or bug depending on your point of view.)

You don't need it UNLESS you are trying to provide
a common root for multiple trees of domains/zone but
that screws up forwarding to the Internet anyways.

Delete the '.' DOT zone -- the forwarder tab will be
activated (at worst a restart of the DNS service.)
Click to expand...
 
Back
Top