similar to: Unbound, dns64 and CentOS 7

On Mon, 30 Mar 2020 at 08:42, Carlos Lopez <clopmz at outlook.com> wrote: > Hi Stephen, > > Many thanks for your answer. Unbound under OpenBSD is compiled with few > options: > > Version 1.9.4 > > That may also be the difference. RHEL-8 is 1.7.3 so I don't know if that added features or config options which the 1.9.4 has in it. > Configure line:

Hi Stephen, Many thanks for your answer. Unbound under OpenBSD is compiled with few options: Version 1.9.4 Configure line: --enable-allsymbols --with-ssl=/usr --with-libevent=/usr --with-libexpat=/usr --without-pythonmodule --with-chroot-dir=/var/unbound --with-pidfile= --with-rootkey-file=/var/unbound/db/root.key --with-conf-file=/var/unbound/etc/unbound.conf --with-username=_unbound

Good morning, I have detected two strange problems with unbound under CentOS8 (fully patched). I have tried same configuration in an OpenBSD host, and these problems do not appear. a/ Error mesage ?connection refused?. I am using this unbound server to resolv DNS records for our internal domain (Bind9 is configured to listen in localhost interface, port 5353 udp and in the same host where

CentOS Errata and Enhancement Advisory 2017:2500 Upstream details at : https://access.redhat.com/errata/RHEA-2017:2500 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2fac524811e1dbf01a6cd6bd931d4628a5adba2d20d0cd97f0cb342ea064b8b3 unbound-1.4.20-23.el6_9.4.i686.rpm

CentOS Errata and Bugfix Advisory 2019:0412 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0412 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 25abb1bca48f050f3b83404860f6f104f6b5385ce36bcd543af505178429a754 unbound-1.4.20-26.el6_10.1.i686.rpm

On Mon, 30 Mar 2020 at 03:47, Carlos Lopez <clopmz at outlook.com> wrote: > Good morning, > > I have detected two strange problems with unbound under CentOS8 (fully > patched). I have tried same configuration in an OpenBSD host, and these > problems do not appear. > > a/ Error mesage ?connection refused?. I am using this unbound server to > resolv DNS records for our

CentOS Errata and Security Advisory 2020:2414 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d7c7de939c7a3dbec81adf688ae2557ca2fc3f18498eb9c09b8896d3b73dd071 unbound-1.6.6-4.el7_8.x86_64.rpm

CentOS Errata and Security Advisory 2020:2642 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2642 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1664066f33b5ffb6a1fd8099211332a04ca7a4e431db14135e8e98690fc582ef unbound-1.6.6-5.el7_8.x86_64.rpm

From: Rafael J. Wysocki <rjw at rjwysocki.net> We leave PCI devices not bound to a driver in D0 during runtime suspend. But they may have a parent which is bound and can be transitioned to D3cold at runtime. Once the parent goes to D3cold, the unbound child may go to D3cold as well. When the child comes out of D3cold, its BARs are uninitialized and thus inaccessible when a driver tries to

On Wed, Feb 21, 2018 at 01:39:34PM +0100, Rafael J. Wysocki wrote: > On Wednesday, February 21, 2018 10:57:14 AM CET Rafael J. Wysocki wrote: > > So if pci_pm_runtime_suspend() is modified to call pci_save_state() > > before returning 0 in the !dev->driver case, we can just move the > > pci_restore_standard_config() invocation in pci_pm_runtime_resume() up > > to the

Hi all, I have a strange case with unbound ... I have defined a stub-zone to query to a secondary DNS server: stub-zone: name: "mydomain.org" stub-addr: 172.22.54.4 stub-zone: name: "54.22.172.in-addr.arpa." stub-addr: 172.22.54.4 ... but it doesn't works: any hostname or IP address is resolved. But if I use "forward": forward-zone: name:

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

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

On Tue, Feb 20, 2018 at 10:29 PM, Bjorn Helgaas <helgaas at kernel.org> wrote: > On Sun, Feb 18, 2018 at 09:38:32AM +0100, Lukas Wunner wrote: >> PCI devices not bound to a driver are supposed to stay in D0 during >> runtime suspend. > > Doesn't "runtime suspend" mean an individual device is suspended while > the rest of the system remains active? >

On Wednesday, February 21, 2018 10:57:14 AM CET Rafael J. Wysocki wrote: > On Tue, Feb 20, 2018 at 10:29 PM, Bjorn Helgaas <helgaas at kernel.org> wrote: > > On Sun, Feb 18, 2018 at 09:38:32AM +0100, Lukas Wunner wrote: > >> PCI devices not bound to a driver are supposed to stay in D0 during > >> runtime suspend. > > > > Doesn't "runtime

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 /

I have installed an Asterisk 1.4 on Suse93 using a FritzCard. Some calls are logged to the ISDN log, but Asterisk is not detecting incoming calls. I wonder whether some other device or process is preventing Asterisk from gaining access to the isdn line? Is there some way to ensure that only Asterisk can listening to the line, or get it to share the line with some other device, such as the fax

PCI devices not bound to a driver are supposed to stay in D0 during runtime suspend. But they may have a parent which is bound and can be transitioned to D3cold at runtime. Once the parent goes to D3cold, the unbound child may go to D3cold as well. When the child comes out of D3cold, its BARs are uninitialized and thus inaccessible when a driver tries to probe. One example are recent hybrid

FYI, while "make" succeeded in this directory on Friday, I ran "make clean" today from the top, then "make" and got this: Making all in examples make[3]: Entering directory `/home/j/w/co/libguestfs/ocaml/examples' ocamlfind ocamlopt \ -warn-error A -I .. mlguestfs.cmxa lvs.ml -o lvs File "lvs.ml", line 11, characters 10-24: Error:

On F12, I'm getting this build failure: ocamlfind ocamlopt -ccopt '-L ../../src/.libs' \ -warn-error A -I .. mlguestfs.cmxa lvs.ml -o lvs File "lvs.ml", line 11, characters 10-24: Error: Unbound value Guestfs.create make[2]: *** [lvs] Error 2 Admittedly with STREQ-related changes, but they seem unrelated...