Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
FACT 4.0.48
-
Night's Watch
-
1
-
NW - 2021-02-03
-
Needs Assessment
-
Bug Fix
-
-
Needs Assessment
Description
Facter 4.0.48 (in Pull Request 2245) resolved a regression in gem-based Facter 4.0.x that did not check for domain name in registry on Windows machines (filed as FACT-2882).
This resolution however prioritizes network interface domain names in favor of the registry information. Puppet 6 and Facter 3 prioritized the registry entries, so this is a regression (or at least, a notable change in behavior).
This is important for domain-joined machines, which store their domain name information in the registry. They may have a network interface with a different domain name received over DHCP, which may be hard to remove depending on the networking circumstances. For these machines where both network adapters have a domain name, and the registry has a domain name, if there is a mismatch, the argument is that the registry is a more safe option to default to.
Attachments
Issue Links
- duplicates
-
FACT-3069 Facter 4.x on MS Azure: wrong domain is used in FQDN
-
- Closed
-