(I was referred to this newsgroup after posting a question in the AD newsgroup.) What would be the impact to remote Outlook/Exchange clients, if certain LDAP SRV records are not registered by the domain-controller at their site? Central Site: - Exchange Servers - Domain Controllers - Exchange clients (Outlook) - Old LDAP-based application Remote Site: - Domain Controller - Exchange clients (Outlook) At the remote site I am considering changing the behavior of the DC so that it does not register the LDAP SRV records when it boots-up. The reason for this is that a certain old application at the Central Site, experiences 90-second logon delays when the Remote Site circuit goes down -- due to old LDAP libraries used by this application. The LDAP SRV records would be not-registered by implementing the group policy: 'DC Locator DNS records not registered by the DCs' The LDAP SRV records are: _ldap._tcp.DnsDomainName. _ldap._tcp.SiteName._sites.DnsDomainName. _ldap._tcp.dc._msdcs.DnsDomainName. _ldap._tcp.SiteName._sites.dc._msdcs.DnsDomainName. _ldap._tcp.pdc._msdcs.DnsDomainName. _ldap._tcp.gc._msdcs.DnsForestName. _ldap._tcp.SiteName._sites.gc._msdcs.DnsForestName. ref: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/ dsbc_nar_sdns.mspx?mfr=true I believe these settings will help the Appilcation at the Central Site to not be impacted by the outage of the Remote Site. However, I want to be sure the Exchange Clients (Outlook) are not impacted by the absence of these records.
I think Outlook won't be impacted. "Robert A" wrote: > (I was referred to this newsgroup after posting a question in the AD > newsgroup.) > > What would be the impact to remote Outlook/Exchange clients, if certain LDAP > SRV records are not registered by the domain-controller at their site? > > Central Site: > - Exchange Servers > - Domain Controllers > - Exchange clients (Outlook) > - Old LDAP-based application > > Remote Site: > - Domain Controller > - Exchange clients (Outlook) > > > At the remote site I am considering changing the behavior of the DC so that > it does not register the LDAP SRV records when it boots-up. The reason for > this is that a certain old application at the Central Site, experiences > 90-second logon delays when the Remote Site circuit goes down -- due to old > LDAP libraries used by this application. > > The LDAP SRV records would be not-registered by implementing the group > policy: 'DC Locator DNS records not registered by the DCs' > > The LDAP SRV records are: > _ldap._tcp.DnsDomainName. > _ldap._tcp.SiteName._sites.DnsDomainName. > _ldap._tcp.dc._msdcs.DnsDomainName. > _ldap._tcp.SiteName._sites.dc._msdcs.DnsDomainName. > _ldap._tcp.pdc._msdcs.DnsDomainName. > _ldap._tcp.gc._msdcs.DnsForestName. > _ldap._tcp.SiteName._sites.gc._msdcs.DnsForestName. > > ref: > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/ > dsbc_nar_sdns.mspx?mfr=true > > > I believe these settings will help the Appilcation at the Central Site to > not be impacted by the outage of the Remote Site. > > However, I want to be sure the Exchange Clients (Outlook) are not impacted > by the absence of these records. >
Outlook basically look for the SRV records for any kind of AD query to be made. For an example if it want to show up the Address Book to the user it has to query the domain controller and not exchange server. Also if you modify the dynamic updates to the dns then DCs wont register themselves at boot up and that may result in RPC dialog box on clients. Outline is making changes in SRV records behaviour in DNS is not recommneded and therefore UNIX based dns servers are not used for name resolution in the site where exchange server is. -- Milind Naphade Messaging Administrator "Robert A" wrote: > (I was referred to this newsgroup after posting a question in the AD > newsgroup.) > > What would be the impact to remote Outlook/Exchange clients, if certain LDAP > SRV records are not registered by the domain-controller at their site? > > Central Site: > - Exchange Servers > - Domain Controllers > - Exchange clients (Outlook) > - Old LDAP-based application > > Remote Site: > - Domain Controller > - Exchange clients (Outlook) > > > At the remote site I am considering changing the behavior of the DC so that > it does not register the LDAP SRV records when it boots-up. The reason for > this is that a certain old application at the Central Site, experiences > 90-second logon delays when the Remote Site circuit goes down -- due to old > LDAP libraries used by this application. > > The LDAP SRV records would be not-registered by implementing the group > policy: 'DC Locator DNS records not registered by the DCs' > > The LDAP SRV records are: > _ldap._tcp.DnsDomainName. > _ldap._tcp.SiteName._sites.DnsDomainName. > _ldap._tcp.dc._msdcs.DnsDomainName. > _ldap._tcp.SiteName._sites.dc._msdcs.DnsDomainName. > _ldap._tcp.pdc._msdcs.DnsDomainName. > _ldap._tcp.gc._msdcs.DnsForestName. > _ldap._tcp.SiteName._sites.gc._msdcs.DnsForestName. > > ref: > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/ > dsbc_nar_sdns.mspx?mfr=true > > > I believe these settings will help the Appilcation at the Central Site to > not be impacted by the outage of the Remote Site. > > However, I want to be sure the Exchange Clients (Outlook) are not impacted > by the absence of these records. >
