> In general, when a DDNS client wants to submit a DDNS > update, it uses the > regular DNS resolver on the host to lookup the SOA record for > the domain in > question. It then contacts the primary nameserver listed in > the SOA record > and submits the update to that server.
I'm not sure that's entirely true. My experience has been that the secondaries actively forward the request on behalf of the client. At least that's what I remember from a few years ago when we started transitioning off BIND onto AD integreated DNS. I seem to recall the entries being logged as coming from the Win2k DNS servers which were secondarying off the BIND server. But in all fairness, I haven't had that kind of setup in 18-24 months, so I can't be sure. -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 17, 2003 6:37 PM > To: NT 2000 Discussions > Subject: Re: DNS Architecture Question > > > On Sun, 17 Aug 2003, at 7:19am, [EMAIL PROTECTED] wrote: > > AD DNS is handled by two root domain servers in our DC. If > one of these > > AD integrated servers is not used as the primary entry in > the DNS portion > > of tcp/ip in the clients & servers at HQ will DNS be auto-updated? > > I'm a bit confused as to exactly what you're asking, but > let me give you a > generic answer and maybe that will do: > > In general, when a DDNS client wants to submit a DDNS > update, it uses the > regular DNS resolver on the host to lookup the SOA record for > the domain in > question. It then contacts the primary nameserver listed in > the SOA record > and submits the update to that server. > > The resolving/caching DNS servers the DDNS client's host is > configured to > send queries to have no necessary relationship with the DNS > servers the > client sends DDNS updates to. > > Also keep in mind that, in the above, "DDNS client" is the > host submitting > the DDNS update, which may not be the same any other host > you're calling a > "client". In particular, your "DHCP server" will often be a > "DDNS client". > > > Basically - the local office with the two secondarys are > going to pull DNS > > from the AD DNS systems but are these records going to > accurate company > > wide? > > As long as your master/slave configuration is proper, the > slaves should > have an exact copy of the DNS zones the AD-integrated > master's have, which > will include any DDNS updates. > > > Can 4 servers located in different geographical areas have > the same AD > > integrated forward zone? In essence, act as one big AD > integrated zone > > trading their records to ensure accuracy across the WAN? > > Yes. That is the idea behind AD-integrated DNS zones. The > only caveat is > that an AD-integrated DNS zone must be hosted on an AD DC. > > I've also never been able to find out if a DDNS client can > submit DDNS > updates to any AD DC, or if it only submits DDNS updates to > the SOA server. > Not that I've looked very hard. > > -- > Ben Scott <[EMAIL PROTECTED]> > | The opinions expressed in this message are those of the > author and do | > | not represent the views or policy of any other person or > organization. | > | All information is provided without warranty of any kind. > | > > > ------ > You are subscribed as [EMAIL PROTECTED] > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&tex t_mode=&lang=english To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED]
