Re: nslookup - sometimes working, sometimes get a time out
From: aks (aks_at_discussions.microsoft.com)
Date: 02/26/05
- Next message: Todd J Heron: "Re: Do I need a "Primary & Secondary" or "Primary & Primary"???"
- Previous message: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- In reply to: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Next in thread: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Reply: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 18:53:02 -0800
Your msg was certainly helpful. Some questions embedded preceded with "aks"
> NSLookup is set pretty quick, and you can always
> use the -time= switch.
aks>>>>> My fear is when AD is installed on three systems, and
replication is performed, there would be no control to increase that
"-time=switch" value when one DC in first domain tries to contact another DC
in the second domain. Unless embedded within the replication code fpr AD
there is a firm retry mechanism in place. Or maybe am thinking too far on
this...
> > I have 2 questions, moving forward:
> >
> > 1. On the server side, I have Forwarders and Zone Transfers configured (in
> > my case both have same set of IP addresses).
> Probably wrong...
>
> > Could you help me know if one
> > supercedes the other or both are needed.
>
> No, they are unrelated. (Except that I can GUESS they probably shouldn't be set >to the same values).
>
> Zone transfer settings on the Secondary to say
> where you GET your copy of a particular zone
> (usually to the Primary but it can be another
> secondary for that same zone). On the Primary
> the corresponding tab is to say which DNS
> servers (secondaries probably) are ALLOWED
> to tranfer FROM the primary.
>
> [This latter setting can be used on Secondaries
> if they also ALLOWS transfers to other secondaries.]
>
> Note that zone transfers are STRICTLY about YOUR
> OWN zones and about TRANSFERRING them among
> your DNS servers for that ONE zone.
aks>>>>>> hmmm, am confused a bit. In my case, I would have a total
of three DC's, and 3 domains, one DC and DNS server for a each domain. Each
DC would be configured with a primary DNS server (running on the same DC,
lets say DC1) and a secondary DNS server running on another DC(lets say DC2),
in another domain. Does this look ok?
aks>>>>> If the above is ok, then the zone transfers will involve
the DNS server on DC1 and DC2 or just DC1 only ? Also, for primary and
secondary zones, is there a recommended naming convention ?
> As for Forwarders, they are a more general setting on
> the SERVER (as a whole, not a particular zone) are
> refer to finding name resolution for zones YOU DON'T
> own on that server set. They are largely about resolving
> the Internet as opposed to YOUR stuff.
aks>>>>> So with my AD integrated DNS setup (as mentioned above), I
would not require Forwarders ? Or have I misunderstood something here.
Would appreciate your help.
Thanks.
- Next message: Todd J Heron: "Re: Do I need a "Primary & Secondary" or "Primary & Primary"???"
- Previous message: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- In reply to: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Next in thread: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Reply: Herb Martin: "Re: nslookup - sometimes working, sometimes get a time out"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
