Re: bind refusing update [never mind]

2020-12-18 Thread Dan Egli
I guess sometimes you just need to look at it in a differnet way. I never noticed it was using the 10.0.2.15 IP to try to update. That's going to be blocked because I don't have the outside world enabled for this server. So let me go ask on the DHCP list why it's insisting on using that

bind refusing update

2020-12-18 Thread Dan Egli
I'm really stumped as to what's going on. I'm trying to get dhcpd to automatically update name records for my internal network. This is NOT going to the public internet by any means. It's just an internal network. But every time either I or dhcpd try to add a record, named refuses to allow it.

Re: BIND through COPR after CentOS

2020-12-18 Thread G.W. Haywood via bind-users
Hi there, On Fri, 18 Dec 2020, Leroy Tennison wrote: ... switching from an rpm world to a deb world ... Not an enormous change but significant. Indeed. I'd suggest that if it's just about BIND, it's easier to grab the source and build it. That way you don't ever have to wait for the

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread Nicolas Bock
Thanks Mark. Am I correct then that I need to either convince the administrator of that DNS to enable DNSSEC or configure my DNS with `dnssec-validation = no`? Thanks, Nick On Fri, Dec 18, 2020 at 3:07 PM Mark Andrews wrote: > Correct it is not validating. Additionally it isn’t even DNSSES

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread Mark Andrews
Correct it is not validating. Additionally it isn’t even DNSSES aware. It will need to be updated for you to validate through it. -- Mark Andrews > On 19 Dec 2020, at 05:07, Nicolas Bock wrote: > > Hi Mark, > > Thanks so much for the reply. I ran this command and am > getting the

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread @lbutlr
On 18 Dec 2020, at 10:56, Nicolas Bock wrote: > ;; ANSWER SECTION: > com. 63779 IN DS 30909 8 2 > E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766 > In other words, the forwarder returns a Delegation Signer > record but not an RRset Signature record. Presumably that > means

Re: BIND through COPR after CentOS

2020-12-18 Thread Leroy Tennison
I should have also mentioned that switching from an rpm world to a deb world (CentOS to Ubuntu) does come with it's learning curve. Some utilities are different, networking configuration in particular is located in different places, then there's the whole package management system. Not an

Re: BIND through COPR after CentOS

2020-12-18 Thread Bruce Johnson
I’m evaluating Oracle Linux to replace CentOS right now for other uses, which Oracle pinky-swears will always be free (beer and speech); it’s essentially another RHEL clone, with some additional stuff for oracle in the repo. I think it’ll end up replacing our CentOS 8 upgrade of ours.

Re: BIND through COPR after CentOS

2020-12-18 Thread Nicolas Bock
On Fri, Dec 18 2020, John Thurston wrote: > We have been using the ISC COPR packages for BIND on CentOS. With the > demise of CentOS, we (along with a few other people on the planet) need > to consider where we will move our applications. > > We have been completely happy with the packages

Re: BIND through COPR after CentOS

2020-12-18 Thread Leroy Tennison
We have been using isc's bind (and dhcp for that matter) which comes with Ubuntu LTS versions and have had good success. Right now we're on Ubuntu 16.04 LTS but that's about to change since the 16.04 revision goes EOL in April. I should mention that our implementation isn't terribly

Re: BIND through COPR after CentOS

2020-12-18 Thread Ondřej Surý
I would add that the Debian packages are at: * 9.11 https://bind.debian.net/bind-esv/ * 9.16 https://bind.debian.net/bind/ * 9.17 https://bind.debian.net/bind-dev/ Ondřej -- Ondřej Surý — ISC (He/Him) > On 18. 12. 2020, at 19:24, Victoria Risk wrote: > >  > >> On Dec 18, 2020, at 10:15 AM,

Re: BIND through COPR after CentOS

2020-12-18 Thread Victoria Risk
> On Dec 18, 2020, at 10:15 AM, John Thurston wrote: > > We have been using the ISC COPR packages for BIND on CentOS. With the demise > of CentOS, we (along with a few other people on the planet) need to consider > where we will move our applications. > > We have been completely happy with

BIND through COPR after CentOS

2020-12-18 Thread John Thurston
We have been using the ISC COPR packages for BIND on CentOS. With the demise of CentOS, we (along with a few other people on the planet) need to consider where we will move our applications. We have been completely happy with the packages provided by ISC through COPR. Does anyone want to

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread Nicolas Bock
Hi Mark, Thanks so much for the reply. I ran this command and am getting the following: $ dig +dnssec ds com @10.0.0.3 ; <<>> DiG 9.10.6 <<>> +dnssec ds com @10.0.0.3 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36260 ;; flags: qr rd ra; QUERY: 1,

issue with domain forwarding

2020-12-18 Thread Frank
   Here is my entire config: My machine IP  =   66.159.32.31   2606:af00:1::3  key "rndc-key" {     algorithm hmac-md5;     secret "y4xt0wQJOiOiZmVaWSMgnQ==";  };  controls {     inet 127.0.0.1 port 953     allow { 127.0.0.1; } keys { "rndc-key"; };  }; acl local

issue with domain forwarding

2020-12-18 Thread Frank
   Hi, I am using bind-9.16.5.   I am having an issue with domain/zone forwarding. Global forwarding works fine. When I configure domain forwarding no request for dns info goes out from the machine. I did a tcpdump to verify this. For bind-9.13.2 the domain forwarding works properly.