Bug #40668
Regenerate /etc/resolv.conf when disabling Domain Controller service
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.
Related issues
Associated revisions
Ticket: #36588
(cherry picked from commit 1d3dd3eb1c80ff34b3f487cb91cc1fc3753ea1e1)
(11.1-stable)
Ticket: #40668
History
#1
Updated by John Hixson over 2 years ago
- Copied from Bug #36588: Regenerate /etc/resolv.conf when disabling Domain Controller service added
#2
Updated by John Hixson over 2 years ago
11.1-stable PR: https://github.com/freenas/freenas/pull/1633
#3
Updated by Dru Lavigne over 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 over 2 years ago
- Status changed from In Progress to Ready for Testing
- Needs Merging changed from Yes to No
#5
Updated by Michael Reynolds over 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
root@freenas:~ # cat /etc/resolv.conf
root@freenas:~ # cat /etc/resolv.conf
root@freenas:~ # cat /etc/resolv.conf
- Generated by resolvconf
search local freebsd.home
nameserver 192.168.1.1
root@freenas:~ # cat /etc/resolv.conf
- Generated by resolvconf
search ixsystems.com freebsd.home
nameserver 127.0.0.1
root@freenas:~ # cat /etc/resolv.conf
- 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 over 2 years ago
- Status changed from Passed Testing to Done