Description of problem: When creating forest trust (as opposed to external trust) with IPA domain from AD side using powershell, Windows machine queries IPA DNS for SRV record which does not exist. Version-Release number of selected component (if applicable): Windows Server 2012 R2, Windows Server 2016 IPA from master branch How reproducible: always Steps to Reproduce: 1. Prepare IPA machine: install ipa server, disable firewall, add DNS forwarder for AD domain 2. Prepare windows machine: setup AD, add DNS forwarder for IPA domain 3. On windows machine open powershell console and execute: [System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest().CreateLocalSideOfTrustRelationship("testrelm.test", 1, "qwertyuiopQq!1") Actual results: Trust not created, output: Exception calling "CreateLocalSideOfTrustRelationship" with "3" argument(s): "The specified domain either does not exist or could not be contacted. Name: "testrelm.test" " At line:1 char:2 + [System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest().CreateL oc ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : ActiveDirectoryServerDownException Expected results: Empty output, trust created. Additional info 1: I enabled logging of DNS requests to bind server and found out that Windows is making following queries: _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.testrelm.test IN SRV _ldap._tcp.gc._msdcs.testrelm.test IN SRV None of those records exists. I can create external trust from powershell using this snippet: [System.DirectoryServices.ActiveDirectory.Forest]::getCurrentDomain().CreateLocalSideOfTrustRelationship("testrelm.test", 1, "qwertyuiopQq!1") I also can create both types of trust using Windows GUI. In those cases there are followng queries in bind log: _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.testrelm.test IN SRV master1.testrelm.test IN A And those records do exist. Additional info 2: I made an experiment -- I created DNS record in IPA server: Record name: _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs SRV record: 0 100 389 master1.testrelm.test. after that step 3 executes successfully.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.