Displaying 20 results from an estimated 10000 matches similar to: "Network Manager / CentOS 7 / local unbound"
2017 Apr 12
1
Network Manager / CentOS 7 / local unbound
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 /
2018 Nov 17
2
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
2018 Nov 17
2
NetworkManager and /etc/resolv.conf
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 preventing NetworkManager
from replacing that file.
I found instructions for Fedora that
2018 Nov 19
3
NetworkManager and /etc/resolv.conf
> 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
2017 Apr 12
0
Network Manager / CentOS 7 / local unbound
On Tue, Apr 11, 2017 at 01:40:21AM -0700, Alice Wonder wrote:
> 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 ?
>
2017 Apr 11
0
Network Manager / CentOS 7 / local unbound
Hi Alice
man NetworkManager.conf
in /etc/NetworkManager/NetworkManager.conf
....
dns=none
....
suomi
On 04/11/2017 10:40 AM, Alice Wonder wrote:
> 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
2017 Feb 14
8
CentOS 7, systemd, NetworkMangler, oh, my
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
2017 Apr 11
1
Network Manager / CentOS 7 / local unbound
From the man page that does tell it not to mess with /etc/resolv.conf -
thank you. That will work.
On 04/11/2017 02:21 AM, anax wrote:
> Hi Alice
> man NetworkManager.conf
>
> in /etc/NetworkManager/NetworkManager.conf
>
> ....
> dns=none
> ....
>
>
*snip*
2017 Feb 16
3
IPv6 broken on Linode
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:
>>>>
>>>>
2017 Feb 16
2
IPv6 broken on Linode
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:
>>>>>
2017 Feb 16
2
IPv6 broken on Linode
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:
>>>>>
2017 Feb 16
2
IPv6 broken on Linode
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:
>> 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
2017 Feb 16
2
IPv6 broken on Linode
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
2017 Feb 16
4
IPv6 broken on Linode
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
2017 Feb 16
1
IPv6 broken on Linode
On 02/16/2017 04:20 AM, James Hogarth wrote:
> On 16 February 2017 at 12:02, James Hogarth <james.hogarth at gmail.com> 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:
2017 Jan 13
4
Unable to edit resolv.conf
On 01/13/2017 05:50 AM, Albert McCann wrote:
>> -----Original Message-----
>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of TE Dukes
>> Sent: Friday, January 13, 2017 7:50 AM
>> To: 'CentOS mailing list' <centos at centos.org>
>> Subject: [CentOS] Unable to edit resolv.conf
>>
>> I changed ISPs and need to update name
2016 Jun 02
2
unbound and ntp issuse
Default install with local_unbound and ntpd can't be functional with
incorrect date/time in BIOS:
Unbound requred correct time for DNSSEC check and refuseing queries
("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
symbolic names like
2016 Jun 02
2
unbound and ntp issuse
Default install with local_unbound and ntpd can't be functional with
incorrect date/time in BIOS:
Unbound requred correct time for DNSSEC check and refuseing queries
("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
symbolic names like
2016 Dec 26
2
Centos7.3-Mate
Hello All,
I have this problem starting Centos7.3 - the official name escapes me at the moment.
I often install Centos7 Minimal, then X Window System, then Mate desktop.
This last step gives me trouble, and I have to run
# yum groupinstall mate --skip-broken
output:
skipped packages:
NetworkManager-I2tp
ldns
libreswan
unbound-libs
xl2tpd
I realise this is probably an issue for EPEL
2019 Feb 13
3
DNSSEC Questions
On 2/12/19 10:55 PM, Alice Wonder wrote:
> DNSSEC keys do not expire. Signatures do expire. How long a signature
> is good for depends upon the software generating the signature, some
> lets you specify. ldns I believe defaults to 60 days but I am not sure.
>
> The keys are in DNSSKEY records that are signed by your Key Signing
> Key and must be resigning before the signature