search for: unbounded

Displaying 20 results from an estimated 659 matches for "unbounded".

2020 Mar 30
2
Some problems with Unbound under CentOS8
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
2020 Mar 30
2
Some problems with Unbound under CentOS8
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
2013 Jul 10
4
nsd can't bind udp socket: Address already in use
Greetings, Unbound 1.4.20 OS X 10.8.4 - Server NSD 3.2.15 I have installed 'unbound' and it works nicely on my client (test purpose) - Client is MacBook Air. I have installed NSD (will be in replacement of BIND) on said client. All is good but when i try to start NSD Error --> nsd can't bind udp socket: address already in use. Everything is configured to bind to 127.0.0.1. #
2020 Mar 30
0
Some problems with Unbound under CentOS8
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:
2020 Mar 30
0
Some problems with Unbound under CentOS8
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
2017 Aug 23
0
CEEA-2017:2500 CentOS 6 unbound Enhancement Update
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
2019 Feb 26
0
CEBA-2019:0412 CentOS 6 unbound BugFix Update
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
2020 Jun 09
0
CESA-2020:2414 Important CentOS 7 unbound Security Update
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
2020 Jun 23
0
CESA-2020:2642 Important CentOS 7 unbound Security Update
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
2020 Jun 10
0
CentOS-announce Digest, Vol 184, Issue 3
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2019 Jul 10
2
Samba and DNSSEC
Hi community, we have tow DCs there works under domain babis.local We are using unbound on our firewall for the interfaces as default DNS-Server. Unbound is activated and has an overwrite from our AD-Domain babis.local to the DCs. When DNSSEC is disabled on unbound, DNS-Queries to dc works perfect. When DNSSEC is activated on unbound, DNS-Queries will be send to root DNS-Servers and i got
2017 Dec 10
2
Problems with dnscrypt's package from EPEL
Not sure if this is a factor yet, but your forwardzone is looking for 3 ports but only 2 ports are configured in the systemd startup.. so are 1/3 of all lookups going to fail? Or is the 6355 a 'given' (aka it will be set up whether 6353 and 6354 are setup?) On 9 December 2017 at 16:45, C. L. Martinez <carlopmart at gmail.com> wrote: > On Sat, Dec 09, 2017 at 10:25:41PM +0100, C.
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 /
2016 Apr 06
5
samba dns
Would prefer to continue to use my NSD/Unbound installs for most DNS (if not all) services. NSD is the authoritative server for the domain, and Unbound is the cache/resolver that the clients connect to. I'd like to not disturb this setup but I'll need the SRV records so that AD works. If the SRV records are fixed I suppose I could host them using NSD, then Samba wouldn't have to be
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
2023 Sep 01
2
Split-horizon question
Hello, NSD 4.7.0 running on FreeBSD 13.X and serving DNSSEC signed zone (say mydomain.org) to the world. I've been approached by a customer with the request to include certain records into mydomain.org zone which will be resolvable only from their premises. I'm thinking to setup a pair of unbound instances, ask the customer to configure conditional forwarding for mydomain.org to those
2018 Mar 03
0
[PATCH v2 1/7] PCI: Restore config space on runtime resume despite being unbound
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
2018 Feb 25
0
[PATCH 1/7] PCI: Restore BARs on runtime resume despite being unbound
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
2016 Oct 03
0
Unbound, dns64 and CentOS 7
Hi all, Is anyone using unbound to do dns64 on CentOS 7? A quick 'unbound -h' shows both 'validator' and 'iterator' modules, but no dns64. Was it just not included or is there a supplementary or alternative package I need to install? I had it working on CentOS 6 and don't recall any special setup, so when I realized the dns64 module was missing from unbound in