Anonymous | Login | 2024-11-21 01:44 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0018761 | ClearOS | app-network - Network Settings | public | 2018-01-19 06:24 | 2018-10-25 10:19 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | tweak | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 7.4.0 | ||||||||
Target Version | 7.5.0 Updates | Fixed in Version | 7.5.0 Updates | ||||||
Summary | 0018761: Review resolver behavior in barebones environment | ||||||||
Description | Local DNS resolution on a ClearOS system is good practice, and in the case of Samba Directory. a requirement. The ClearOS Resolver API manages the resolver files as follows: 1) If Samba Directory is installed: - /etc/resolv.conf points to Samba Directory DNS - /etc/resolv-peerdns.conf contains the upstream DNS servers (via DHCP or PPPoE) - /etc/samba/smb.conf points to upstream DNS servers 2) If the DNS app (Dnsmasq) is installed and running - /etc/resolv.conf points to 127.0.0.1 (Dnsmasq) - /etc/resolv-peerdns.conf contains the upstream DNS servers (via DHCP or PPPoE) 3) Otherwise, make sure /etc/resolv.conf is in good shape This last scenario is rare on a ClearOS install (DNS/dnsmasq is running by default), but will be more common in a ClearVM environment. Sanity check. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||