Hi All,
in our company we have implemented Active Directory, served by four DCs - dc1, dc2, dc3 and dc4, which maintain the domain domain.local, single forest single domain. We are using an InfoBlox applience as DNS server instead of Microsoft AD integrated DNS. The IP address of InfoBlox appliance is set on each domain controller as primary name server on the network card. As this AD implementation was inherited from the previous administrator (which suddenly left the company before I take his place) with no documentation at all what I found is that an AD integrated DNS server exists on dc2. This AD integrated DNS obviously was built during the initial configuration of Active Directory, it holds the zone domain.local with all supporting zones as _msdcs.domain.local etc. At the InfoBlox's side the zone was configured and it acts perfectly as a name server, every computer or server when added to domain registers itself in the InfoBlox, _msdcs.domain.local, _gc, _kerberos, _ldap zones and records are OK. We are facing an issue with ldap localization with Oracle BI software, which is installed on a domain member server. Oracle BI is set to work with AD users and for this purpose a LDAP connector was set. As a LDAP server I set domain.local, there is a dedicated domain user which is set in Oracle BI to perform LDAP queries, the user is specified with its distinguished name. When Oracle BI queries domain the users are listed in the Oracle BI. However, when I shut down dc2 Oracle BI is no longer able to perform LDAP queries. It seems that the connector somehow prefers AD integrated DNS instead the InfoBlox's DNS when performing LDAP queries. I have added DNS server role on dc1 (whith dc2 powered on), all the zones are transferred from dc2. When I shutdown dc2 the Oracle BI works perfectly with LDAP queries. The conclusion I made is that when there is no AD integrated DNS up and running Oracle BI is unable to perform LDAP queries even with specified in its network settings InfoBlox name server with all zones and records. Does anybody know what would be the reason this issue to occurs?
PS. Forgot to mention that on both AD Integrated DNS and InfoBlox all the _ldap records are set with priority 0 and weight 100.
in our company we have implemented Active Directory, served by four DCs - dc1, dc2, dc3 and dc4, which maintain the domain domain.local, single forest single domain. We are using an InfoBlox applience as DNS server instead of Microsoft AD integrated DNS. The IP address of InfoBlox appliance is set on each domain controller as primary name server on the network card. As this AD implementation was inherited from the previous administrator (which suddenly left the company before I take his place) with no documentation at all what I found is that an AD integrated DNS server exists on dc2. This AD integrated DNS obviously was built during the initial configuration of Active Directory, it holds the zone domain.local with all supporting zones as _msdcs.domain.local etc. At the InfoBlox's side the zone was configured and it acts perfectly as a name server, every computer or server when added to domain registers itself in the InfoBlox, _msdcs.domain.local, _gc, _kerberos, _ldap zones and records are OK. We are facing an issue with ldap localization with Oracle BI software, which is installed on a domain member server. Oracle BI is set to work with AD users and for this purpose a LDAP connector was set. As a LDAP server I set domain.local, there is a dedicated domain user which is set in Oracle BI to perform LDAP queries, the user is specified with its distinguished name. When Oracle BI queries domain the users are listed in the Oracle BI. However, when I shut down dc2 Oracle BI is no longer able to perform LDAP queries. It seems that the connector somehow prefers AD integrated DNS instead the InfoBlox's DNS when performing LDAP queries. I have added DNS server role on dc1 (whith dc2 powered on), all the zones are transferred from dc2. When I shutdown dc2 the Oracle BI works perfectly with LDAP queries. The conclusion I made is that when there is no AD integrated DNS up and running Oracle BI is unable to perform LDAP queries even with specified in its network settings InfoBlox name server with all zones and records. Does anybody know what would be the reason this issue to occurs?
PS. Forgot to mention that on both AD Integrated DNS and InfoBlox all the _ldap records are set with priority 0 and weight 100.