Description of problem: setup was need DNS servers in resolve conf to resolve domain. Entered in setup DNS dont used, Version-Release number of selected component (if applicable): How reproducible: 1. echo "8.8.8.8" > /etc/resolv.conf 2. Try add AD with local DNS Expected results: Resolving in setup must use entered DNS.
When it's not resolved by server in resolv.conf, you should be asked a question: "Please enter space seperated list of Active Directory DNS Servers names" Where you specify additional AD DNS servers, which are used. This question you won't get or using that servers it doesnt' work? Can you please send a log? Thanks.
I don't have logs. I was setup its few weeks ago. Yes. it's ask but check for login or search user does not woek without adding DNS to resolv.conf. After install i remove dns from resolve conf and all work. It's look that setup don't use DNS what i posted to "Please enter space seperated list of Active Directory DNS Servers names". Errors was look like "Can't resolve SERVERDC.local". Setup Found AD tree. It's found main DC server name in AD, but can't connect to it, becouse can't resolve its IP.
aaa-ldap currently provides an option to specify DNS servers to resolve LDAP server name which cannot be resolved by DNS configuration of the host. This is pretty non standard (it's supported only by unboundid-ldapsdk library used by aaa-ldap) and it bypasses standard host DNS configuration which could lead to issues. oVirt relies on valid DNS configuration and this specific advanced configuration shouldn't be available in aaa-ldap setup tool, which offers only basic configuration of aaa-ldap. That's why we decided to remove this option from aaa-ldap setup tool.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Fix will be contained in ovirt-engine-extension-aaa-ldap-1.1.3
Verified with: ovirt-engine-extension-aaa-ldap-setup-1.1.3-1.el6ev.noarch No option for custom DNS during aaa-ldap-setup.