similar to: NetworkManager and /etc/resolv.conf

On 11/17/2018 07:01 AM, Alice Wonder wrote: > On 11/17/2018 06:43 AM, Alice Wonder wrote: >> CentOS 7.5 image running on linode. >> >> unbound running on localhost. >> >> Have to use a cron job once a minute to keep /etc/resolv.conf using >> the localhost for name resolution - whenever NetworkManager gets >> restarted (usually only a system boot) it

> On 11/17/18 8:31 AM, Alice Wonder wrote: >> On 11/17/2018 07:01 AM, Alice Wonder wrote: >>> On 11/17/2018 06:43 AM, Alice Wonder wrote: >>>> CentOS 7.5 image running on linode. >>>> >>>> unbound running on localhost. >>>> >>>> Have to use a cron job once a minute to keep /etc/resolv.conf using >>>> the

On 11/17/18 8:31 AM, Alice Wonder wrote: > On 11/17/2018 07:01 AM, Alice Wonder wrote: >> On 11/17/2018 06:43 AM, Alice Wonder wrote: >>> CentOS 7.5 image running on linode. >>> >>> unbound running on localhost. >>> >>> Have to use a cron job once a minute to keep /etc/resolv.conf using >>> the localhost for name resolution - whenever

On 11/19/18 6:49 AM, Simon Matter wrote: >> On 11/17/18 8:31 AM, Alice Wonder wrote: >>> On 11/17/2018 07:01 AM, Alice Wonder wrote: >>>> On 11/17/2018 06:43 AM, Alice Wonder wrote: >>>>> CentOS 7.5 image running on linode. >>>>> >>>>> unbound running on localhost. >>>>> >>>>> Have to use a cron

Hello list - http://unix.stackexchange.com/questions/90035/how-to-set-dns-resolver-in-fedora-using-network-manager That says it works for CentOS 5 and I *suspect* the methods there (3 listed) would work, but what is the best way with NetworkManager to set it up to use the localhost for DNS ? I'm paranoid about DNS spoofing and really prefer to have a local instance of DNSSEC enforcing

On 11/17/2018 06:43 AM, Alice Wonder wrote: > CentOS 7.5 image running on linode. > > unbound running on localhost. > > Have to use a cron job once a minute to keep /etc/resolv.conf using the > localhost for name resolution - whenever NetworkManager gets restarted > (usually only a system boot) it gets over-written. > > It seems every distro has a different way of

https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 I can not figure out what I need to do. Apparently according to linode support, the VM is trying to grab an IPv6 address with some privacy stuff enabled by default causing it to not grab the IPv6 address that is assigned to me. Nothing I have tried seems to work, and it seems that Linode support are far more familiar with

OR just make the file immutable if it's so critical to you. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Jon LaBadie" <jcu at labadie.us> > To: "CentOS mailing list" <centos at centos.org> > Sent: Wednesday, 12 April, 2017 07:16:22 > Subject: Re: [CentOS] Network Manager / CentOS 7 /

Hello all, I'm getting frustrated attempting to understand; I googled and asked folks and am unable to get a straight answer. 1. How is the /etc/resolv.conf file maintained ? I do not seem to get a consistent result when I save resolv.conf configuration from GUI or by hand using vim /etc/resolv.conf. a. Sometimes I the entries toggles between the two entries: # generated by

NetworkManager used to work fine for me but during the last few installations its a big hurdle in the wireless connectivity. I'm using Madwifi and its interface is correctly listed and working but I cannot connect to any wifi AP without NetworkManager. I've two interfaces: eth0 and wifi0. Starting NetworkManager doesn't show any notification icon in the top right in gnome and I believe

I would like to use dnsmasq to cache nameserver query results, and I have set dhcp to prepend the 127.0.0.1 name-server to the list of nameservers. dnsmasq would then automatically exclude the localhost as a name server and use all the others from the list provided by dhcp. But it was too nice to be true, because NetworkManager was there, ready to mess up anything I try to do, including the

On 02/13/2017 11:36 AM, peter.winterflood wrote: > On 13/02/17 16:49, James Hogarth wrote: >> On 13 February 2017 at 16:17, peter.winterflood >> <peter.winterflood at ossi.co.uk> wrote: >>> >>> >>> there's a really good solution to this. >>> >>> yum remove NetworkManager* >>> >>> chkconfig network on

On 02/16/2017 02:32 AM, James Hogarth wrote: > On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:03 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>>>>

My machine has a static IP, with dhcp and IPv6 disabled. Every time I reboot, some process rewrites /etc/resolv.conf, including a comment about dhcpclient. The only package I have installed that shows up in "rpm -qa|grep -i dhcp" is dhcpv6-client-1.0.10-16.el5, and nothing in there is named dhcpclient. I'd like to figure out what software is rewriting this file and why. man 5

On 02/16/2017 03:28 AM, James Hogarth wrote: > On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:32 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>>>

Hi, I am facing issue stoping NetworkManager to update resolv.cfg, I am using below configuration for eth0 interface: TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eth0 UUID=93b90a46-dab5-4a67-8fd0-fefe8874a8b9 DEVICE=eth0 ONBOOT=no PEERDNS=no PEERROUTES=yes

On 02/16/2017 02:03 AM, James Hogarth wrote: > On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>> >>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, >>> Alice Wonder <alice at domblogger.net> wrote: >>>> >>>>

On 16 February 2017 at 11:46, James Hogarth <james.hogarth at gmail.com> wrote: > On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 03:28 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:32 AM, James

given machine with C6 x86_64 (seen on C 6.6 but also before and probably still present on C6.7) only 1 interface, there is dhcp on this network (for kickstarting) but the machines have static ip's, and NO networkmanager installed contents of resolv.conf search some.domain.here nameserver x.x.x.x #dns1 nameserver y.y.y.y #dns2 change resolv.conf to: search some.newdomain.here nameserver

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me