RE: bind 9.16.2 on centos6

2020-04-18 Thread Gilles Buisson
On our last Centos 6 server, we managed building Bind 9.16.1 with the help
of Okay repo (http://repo.okay.com.mx)

Installed Packages
libuv-debuginfo.x86_64   1:1.9.1-4.el6   @okay
libuv-devel.x86_64   1:1.9.1-4.el6   @okay
libuv-static.x86_64   1:1.9.1-4.el6   @okay
libuv1.x86_641:1.9.1-4.el6   @okay

Hope this help

Regards

Gilles

-Original Message-
From: bind-users  On Behalf Of Carl
Byington via bind-users
Sent: Saturday, April 18, 2020 22:46
To: bind-users 
Subject: bind 9.16.2 on centos6

Centos6, although old, is still supported, so it would be nice to get
9.16.2 running on that. This is my first attempt at building 9.16.x. 

I pulled the libuv source rpm from Centos7, made some minor changes to the
spec file, and built libuv 1.34.0. 

Using that, bind 9.16.2 builds to an rpm and installs, but crashes on
startup. 

(gdb) bt
#0  0x0033772324f5 in raise (sig=6) 
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x003377233cd5 in abort () at abort.c:92
#2  0x7f2f5fba9cc4 in uv_async_send () from /usr/lib64/libuv.so.1
#3  0x7f2f5fdf6329 in isc_nm_pause (mgr=0x7f2f5f945010) at
netmgr.c:322
#4  0x7f2f5fe06e07 in isc_task_beginexclusive (task0=) 
at task.c:1662
#5  0x0043613f in load_configuration ( 
filename=0x7f2f59eac770 "\030\307\060O/\177", server=0x7f2f5c0a8010, 
first_time=true) at ./server.c:8309
#6  0x0043a27d in run_server (task=,
event=0x0) 
at ./server.c:9660
#7  0x7f2f5fe07b21 in dispatch (queuep=) 
at task.c:1152
#8  run (queuep=) at task.c:1344
#9  0x003c18807aa1 in start_thread (arg=0x7f2f59ead700) 
at pthread_create.c:301
#10 0x0033772e8c4d in clone () 
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 


Is this the same issue previously reported against 9.16.1? That was
apparently resolved by downgrading to libuv 1.35. In my case, I can try to
upgrade to 1.35. 

The test in configure.ac in the bind source checks that the version of libuv
is >= 1.0.0. 





___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: bind 9.16.2 on centos6

2020-04-18 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


> Is this the same issue previously reported against 9.16.1? That was
> apparently resolved by downgrading to libuv 1.35. In my case, I can
> try
> to upgrade to 1.35.

Nope, libuv 1.35.0 does not change the crash.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAl6bdZAACgkQL6j7milTFsFmnwCfZC0IxRYScs3qNSxDJ67q31qH
8n4AnRUFgWKhTeachVnl/yihhaz+sm6v
=Qnan
-END PGP SIGNATURE-


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


bind 9.16.2 on centos6

2020-04-18 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Centos6, although old, is still supported, so it would be nice to get
9.16.2 running on that. This is my first attempt at building 9.16.x.

I pulled the libuv source rpm from Centos7, made some minor changes to
the spec file, and built libuv 1.34.0.

Using that, bind 9.16.2 builds to an rpm and installs, but crashes on
startup.

(gdb) bt
#0  0x0033772324f5 in raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x003377233cd5 in abort () at abort.c:92
#2  0x7f2f5fba9cc4 in uv_async_send () from /usr/lib64/libuv.so.1
#3  0x7f2f5fdf6329 in isc_nm_pause (mgr=0x7f2f5f945010) at
netmgr.c:322
#4  0x7f2f5fe06e07 in isc_task_beginexclusive (task0=)
at task.c:1662
#5  0x0043613f in load_configuration (
filename=0x7f2f59eac770 "\030\307\060O/\177", server=0x7f2f5c0a8010,
first_time=true) at ./server.c:8309
#6  0x0043a27d in run_server (task=,
event=0x0)
at ./server.c:9660
#7  0x7f2f5fe07b21 in dispatch (queuep=)
at task.c:1152
#8  run (queuep=) at task.c:1344
#9  0x003c18807aa1 in start_thread (arg=0x7f2f59ead700)
at pthread_create.c:301
#10 0x0033772e8c4d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115


Is this the same issue previously reported against 9.16.1? That was
apparently resolved by downgrading to libuv 1.35. In my case, I can try
to upgrade to 1.35.

The test in configure.ac in the bind source checks that the version of
libuv is >= 1.0.0.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAl6bZrgACgkQL6j7milTFsFDTQCfUw2AaohJDFUN1NljCf6RDs1X
6QsAn3Dh+4VK1t+k2f7mO/cNjPM+fvL9
=Ilbj
-END PGP SIGNATURE-


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Batch updating all DNS records on my Bind server

2020-04-18 Thread Tony Finch
@lbutlr  wrote:
>
> Is it possible to batch update all the domains? Looking at nsupdate it
> looks like I have to step through and do every domain individually.

An UPDATE request can change many records, so long as they are all in the
same zone, and so long as they fit in the 64KB limit of DNS message size.
I find one request is usually enough for routine changes, but if you are
doing a bulk update to a large zone, you will need to split the changes
across mulitiple update requests.

You might find nsdiff helpful, both to verify that your bulk changes are
what you expect, and because it will split large updates into multiple
requests automatically. It's still one-zone-at-a-time, though. A
quick-and-dirty starting point might be roughly

dig axfr $zone |
sed 's/oldprefix/newprefix/' |
nsdiff $zone /dev/stdin |
nsupdate -l

https://dotat.at/prog/nsdiff/

Tony.
-- 
f.anthony.n.finchhttp://dotat.at/
North Utsire, South Utsire: Variable 3 or less. Smooth or slight, occasionally
moderate at first. Fair. Good.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Batch updating all DNS records on my Bind server

2020-04-18 Thread Reindl Harald


Am 18.04.20 um 17:39 schrieb @lbutlr:
> On 18 Apr 2020, at 09:34, Reindl Harald  wrote:
>> Am 18.04.20 um 17:23 schrieb @lbutlr:
>>> Is it possible to batch update all the domains? Looking at nsupdate it 
>>> looks like I have to step through and do every domain individually.
> 
>> well, where is the issue iterate all your domains in a bash script as
>> you don't seem to have some sql backed admin interface?
> 
> “nsupdate does not support batch updates” would have been shorter

dunno if it can but i fail to imagine how that should work - how does it
know about your domains at all?

the loaded zones can be a wild mix of forward and reverse zones, what
exactly should it replace

doing something with 10, 200, 1000 zones is where admin software has
it's place - in the backend i coded in 2008 i can write pure hostnames
of our own zone as value for A records

when generate a zone from the database wthis will be replaced by the
current ip in our own one and an additional button triggers "rebuild all
zones from scratch"

more or less one night the days back and maybe with the "virtual CNMAE
for A records" or however one will call it a second night and the reason
for that was, well, a ipchange for the whole network
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Batch updating all DNS records on my Bind server

2020-04-18 Thread @lbutlr
On 18 Apr 2020, at 09:34, Reindl Harald  wrote:
> Am 18.04.20 um 17:23 schrieb @lbutlr:
>> Is it possible to batch update all the domains? Looking at nsupdate it looks 
>> like I have to step through and do every domain individually.

> well, where is the issue iterate all your domains in a bash script as
> you don't seem to have some sql backed admin interface?

“nsupdate does not support batch updates” would have been shorter.



-- 
showing snuffy is when Sesame Street jumped the shark


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Batch updating all DNS records on my Bind server

2020-04-18 Thread Reindl Harald


Am 18.04.20 um 17:23 schrieb @lbutlr:
> We are making some changes to our NSP account and the NSP is threatening to 
> change our IP block. This means I will have to update all the domains on the 
> system (all using DNSSEC). We are still arguing with them since there is no 
> technical reason for forcing this change on us, but chances are they will 
> prove to be inflexible.
> 
> Is it possible to batch update all the domains? Looking at nsupdate it looks 
> like I have to step through and do every domain individually.
> 
> The only occurrence of ‘batch’ on the nsupdate man page is:
> 
>  -vUse TCP even for small update requests. By default, nsupdate uses
>UDP to send update requests to the name server unless they are too
>large to fit in a UDP request in which case TCP will be used. TCP
>may be preferable when a batch of update requests is made.

well, where is the issue iterate all your domains in a bash script as
you don't seem to have some sql backed admin interface?

a global ipchange is something you should have pre-scripted unless you
have a provider independent ip-range
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Batch updating all DNS records on my Bind server

2020-04-18 Thread @lbutlr
We are making some changes to our NSP account and the NSP is threatening to 
change our IP block. This means I will have to update all the domains on the 
system (all using DNSSEC). We are still arguing with them since there is no 
technical reason for forcing this change on us, but chances are they will prove 
to be inflexible.

Is it possible to batch update all the domains? Looking at nsupdate it looks 
like I have to step through and do every domain individually.

The only occurrence of ‘batch’ on the nsupdate man page is:

 -vUse TCP even for small update requests. By default, nsupdate uses
   UDP to send update requests to the name server unless they are too
   large to fit in a UDP request in which case TCP will be used. TCP
   may be preferable when a batch of update requests is made.


-- 
'They say that whoever pays the piper calls the tune.' 'But,
gentlemen,' said Mr Saveloy, 'whoever holds a knife to the
piper's throat writes the symphony.' --Interesting Times


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users