RE: [Non-DoD Source] Re: BIND installed on a Solaris 11.4 x 86 virtual server

2020-06-01 Thread DeCaro, James John (Jim) CIV DISA FE (USA) via bind-users
Also, BIND binaries are located in /usr/bin and /usr/sbin --sorry I forgot to mention that. I went ahead and re-compiled with ./configure --enable-full-report --with-gssapi=krb5-config --sysconfdir=/etc --with-openssl=/usr/local --localstatedir=/var --enable-fixed-rrset and installed it,

RE: [Non-DoD Source] Re: BIND installed on a Solaris 11.4 x 86 virtual server

2020-06-01 Thread DeCaro, James John (Jim) CIV DISA FE (USA) via bind-users
named -c /etc/named.conf -g 01-Jun-2020 15:02:22.034 starting BIND 9.16.3 (Stable Release) 01-Jun-2020 15:02:22.034 running on SunOS i86pc 5.11 11.4.20.4.0 01-Jun-2020 15:02:22.034 built with '--with-gssapi=krb5-config' 'LDFLAGS=-L/usr/local/lib -R/usr/local/lib'

Re: BIND installed on a Solaris 11.4 x 86 virtual server

2020-06-01 Thread Anand Buddhdev
On 01/06/2020 20:08, DeCaro, James John (Jim) CIV DISA FE (USA) via bind-users wrote: Hi Jim, Installed BIND 9.16.3 and I discovered that the SMF dns/server is trying to read named.conf from /usr/local/etc/: "/usr/local/etc/named.conf: file not found". I am trying to figure out how point

BIND installed on a Solaris 11.4 x 86 virtual server

2020-06-01 Thread DeCaro, James John (Jim) CIV DISA FE (USA) via bind-users
Installed BIND 9.16.3 and I discovered that the SMF dns/server is trying to read named.conf from /usr/local/etc/: "/usr/local/etc/named.conf: file not found". I am trying to figure out how point named to read /etc/named.conf. I did try re-compiling BIND with different switches but it resulted

Re: nsupdate - adding large/split TXT record (2048 bit DKIM key)

2020-06-01 Thread vom513
Done: https://gitlab.isc.org/isc-projects/bind9/-/issues/1907 Thanks. > On Jun 1, 2020, at 7:08 AM, Ondřej Surý wrote: > > I think it’s reasonable for nsupdate to do the chunking on itself. Patches > are always welcome, but if you

Re: nsupdate - adding large/split TXT record (2048 bit DKIM key)

2020-06-01 Thread vom513
> On Jun 1, 2020, at 6:50 AM, Andreas S. Kerber wrote: > > Yeah, I had troubles with those 2048 bit DKIM records too. nsupdate will need > it like this: > > server X.X.X.X > zone ag-trek.de > update add test.ag-trek.de. 86400 IN TXT"v=DKIM1; >

Re: nsupdate - adding large/split TXT record (2048 bit DKIM key)

2020-06-01 Thread Ondřej Surý
I think it’s reasonable for nsupdate to do the chunking on itself. Patches are always welcome, but if you can start by creating issue for us, it would be very much welcome. I can’t offer you any timeframe, but at least it won’t get lost. Ondrej -- Ondřej Surý ond...@isc.org > On 1 Jun 2020, at

Re: nsupdate - adding large/split TXT record (2048 bit DKIM key)

2020-06-01 Thread Andreas S. Kerber
On Mon, Jun 01, 2020 at 04:11:43AM -0400, vom513 wrote: > Can anyone point me to an example of how to do this ? I have a script that > rotates my DKIM keys, and uses nsupdate to publish. With 1024 bit - I must > be getting by by the skin of my teeth… > > When I try 2048 bit, the record is

Re: nsupdate: using "wildcard" TTL when removing specific record

2020-06-01 Thread Mark Andrews
TTL is ignored on delete if it present. It is set to 0 when sending. 2.5.4 - Delete An RR From An RRset RRs to be deleted are added to the Update Section. The NAME, TYPE, RDLENGTH and RDATA must match the RR being deleted. TTL must be specified as zero (0) and will otherwise be

nsupdate: using "wildcard" TTL when removing specific record

2020-06-01 Thread Petr Bena
Hello, Is there any way to tell nsupdate to delete specific record with ANY TTL value? For example I have following record: record.domain.org 3500 A 1.2.3.4 I want to delete exactly that record (A with IP 1.2.3.4), except I don't know what the TTL is, normally, if I knew the TTL, I would do

nsupdate - adding large/split TXT record (2048 bit DKIM key)

2020-06-01 Thread vom513
Hello, Can anyone point me to an example of how to do this ? I have a script that rotates my DKIM keys, and uses nsupdate to publish. With 1024 bit - I must be getting by by the skin of my teeth… When I try 2048 bit, the record is obviously longer. All of my attempts of running it through

Re: 9.16.3 make tests on centos 8

2020-06-01 Thread Petr Menšík
It seems okay to test it. It just should be able to skip the test if chosen user cannot reach test directory. This test also fails on 9.11.19 version. On 6/1/20 1:38 AM, Mark Andrews wrote: > Opened ticket. That system test appears to be very linux capabilities > specific when run as root. >

Re: 9.16.3 make tests on centos 8

2020-06-01 Thread Petr Menšík
Hi, I have fixed this on RHEL by chmod o+x $HOME before build. I think it should autodetect nobody's access at least to current $HOME. Not sure what would be the best fix. named-checkconf is missing user switch. That check should be skipped if not configured properly. I am unsure which bind