Project

General

Profile

Bug #11006

idmap fall-back to DC discovery is broken

Added by Gordon Ross 5 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
2019-05-14
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

If you configure an incorrect site_name property in idmap, joining an AD domain fails when it should be able to find an AD server using the regular (not site-specific) DNS query.

History

#1

Updated by Gordon Ross 5 months ago

  • Description updated (diff)
  • Status changed from New to In Progress

It turns out fall-back from site-specific DC location to global DC location has never worked.
In libadutils, we should try both kinds of DNS query before we give up.

#2

Updated by Gordon Ross 5 months ago

Testing: Configure a non-existent site and verify that DC location still works.

#3

Updated by Electric Monk 4 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

git commit d0bed8f264c913bf83285b0beed22bd3a9f7eb08

commit  d0bed8f264c913bf83285b0beed22bd3a9f7eb08
Author: Gordon Ross <gwr@nexenta.com>
Date:   2019-06-06T15:14:05.000Z

    11006 idmap fall-back to DC discovery is broken
    Reviewed by: Evan Layton <evan.layton@nexenta.com>
    Reviewed by: Matt Barden <matt.barden@nexenta.com>
    Approved by: Garrett D'Amore <garrett@damore.org>

Also available in: Atom PDF