Project

General

Profile

Bug #36588

Regenerate /etc/resolv.conf when disabling Domain Controller service

Added by Andrew Walker about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
John Hixson
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

This has been observed on two customer systems who accidentally turned on DC role while joined to active directory. When in DC role, nameserver switches to 127.0.0.1. Turning off Domain Controller service does restore /etc/resolv.conf to a proper state.

beforedc.png (116 KB) beforedc.png before turning on DC Rishabh Chauhan, 07/20/2018 08:20 AM
dcturnedon.png (108 KB) dcturnedon.png when DC is turned on Rishabh Chauhan, 07/20/2018 08:20 AM
postdc.png (104 KB) postdc.png after turning off DC Rishabh Chauhan, 07/20/2018 08:20 AM
22127
22131
22135

Related issues

Related to FreeNAS - Bug #25184: Nameserver in GUI does not reflect what is set in resolv.conf when DC is enabledClosed
Copied to FreeNAS - Bug #40668: Regenerate /etc/resolv.conf when disabling Domain Controller serviceDone

Associated revisions

Revision 1d3dd3eb (diff)
Added by John Hixson about 2 years ago

Ticket: #36588

Revision 602f2f9f (diff)
Added by John Hixson about 2 years ago

Ticket: #36588 (cherry picked from commit 1d3dd3eb1c80ff34b3f487cb91cc1fc3753ea1e1) (11.1-stable) Ticket: #40668

Revision 712a0ac4
Added by John Hixson about 2 years ago

Merge pull request #1633 from freenas/freenas/11.1-stable-ticket-40668 Ticket: #36588

History

#1 Updated by Andrew Walker about 2 years ago

#2 Updated by Dru Lavigne about 2 years ago

  • Assignee changed from Release Council to John Hixson

#3 Updated by John Hixson about 2 years ago

Revert the revert? I'm not clear on why it was reverted in the first place. Does anyone else know why before I revert revert?

#4 Updated by John Hixson about 2 years ago

Nevermind, chased the commit revert message and vaguely recall what happened. I think it's okay to just do this single fix here.

#6 Updated by John Hixson about 2 years ago

  • Status changed from Unscreened to Ready for Testing

#7 Updated by Dru Lavigne about 2 years ago

  • Subject changed from /etc/resolv.conf needs to be regenerated when we stop the Domain Controller service to Regenerate /etc/resolv.conf when disabling Domain Controller service
  • Target version changed from Backlog to 11.2-BETA2
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#8 Updated by Rishabh Chauhan about 2 years ago

22127
22131
22135

The fix response is as expected...refer screenshots
resolv.conf nameserver goes back to the initial state(set in the UI) after Dc is turned off

#9 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

#10 Updated by John Hixson about 2 years ago

  • Copied to Bug #40668: Regenerate /etc/resolv.conf when disabling Domain Controller service added

#11 Updated by Dru Lavigne about 2 years ago

  • Related to Bug #25184: Nameserver in GUI does not reflect what is set in resolv.conf when DC is enabled added

Also available in: Atom PDF