Project

General

Profile

Bug #40668

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

Added by John Hixson about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
John Hixson
Category:
OS
Target version:
11.1-U6
Seen in:
11.1-U5
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
23628
23632
23636

Related issues

Copied from FreeNAS - Bug #36588: Regenerate /etc/resolv.conf when disabling Domain Controller serviceDone

Associated revisions

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

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

History

#1 Updated by John Hixson about 2 years ago

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

#2 Updated by John Hixson about 2 years ago

#3 Updated by Dru Lavigne about 2 years ago

  • Status changed from Unscreened to In Progress
  • Needs QA changed from No to Yes
  • Needs Merging changed from No to Yes

#4 Updated by Dru Lavigne about 2 years ago

  • Status changed from In Progress to Ready for Testing
  • Needs Merging changed from Yes to No

#5 Updated by Michael Reynolds about 2 years ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No
Checked resolv.conf before setting up Domain Controller
root@freenas:~ # cat /etc/resolv.conf
  1. Generated by resolvconf
    search local freebsd.home
    nameserver 192.168.1.1
Setup/enabled the Domain Controller service, checked resolv.conf
root@freenas:~ # cat /etc/resolv.conf
  1. Generated by resolvconf
    search ixsystems.com freebsd.home
    nameserver 127.0.0.1
Disabled the Domain Controller, checked resolv.conf
root@freenas:~ # cat /etc/resolv.conf
  1. Generated by resolvconf
    search local freebsd.home
    nameserver 192.168.1.1

Stopping the Domain Controller service regenerates resolv.conf

#6 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF