ELF(404 (444  TTT++ . > >D4.4>4>hhhDDPtd)))QtdRtd . > >/lib/ld-linux.so.2GNUGNUZ ^GH0 I@)029BE|a*KXj|3rqX}q"C*Q yLv>/ Wb( $@7dA`AgD<@p C@@  +@libdns.so.69isc_base64_totext__gmon_start___Jv_RegisterClassesisc___mem_getisc__buffer_initisc__buffer_usedregionisc_entropy_detachisc_result_totextisc___mem_putisc__mem_createdst_key_generatedst_key_tobufferdst_key_free_finidns_rootnamedst_lib_destroydst_lib_initlibisc.so.62isc_commandline_parseisc_commandline_argumentisc_entropy_destroysourceisc_file_safecreateisc__mem_destroyisc_entropy_usebestsourceisc_commandline_errprintisc_entropy_createisc__mem_statsisc_file_prognameisc_commandline_indexisc_commandline_optionisc_mem_debugginglibpthread.so.0__errno_locationlibc.so.6_IO_stdin_usedfflush__printf_chkexitputsgetpwnam__fprintf_chkfchownfputcfclosestderr__snprintf_chkfileno__vfprintf_chk__cxa_finalize__libc_start_mainferror__stack_chk_fail_edata__bss_start_end_fp_hwverboseGLIBC_2.0GLIBC_2.1GLIBC_2.4GLIBC_2.1.3GLIBC_2.3.4< ii K]ii Uii _ii Ksi iti u???@?? ? ???!?%?&?.?/0?4?8?D$HD$LD$|t$TD$D$4$JD$$T$(t$D$ D$CT$D$D$x$q|$,ID$X|$$D$D$`D$D$D$D$$$$T$t&UWVS"LD$pt$`l$d|$l$D$<4$D$,D$$0 $Ð\$D$$GT!t$$t2pD$ $;D$t$$w\$t$Ív#ߐUWVS l$0g)t)1D$8,$D$D$4D$9u߃[^_] ÐSan UVS=J t&Ћu[^]S[ C[Usage: %s [-a alg] [-k keyname] [-r randomfile] [-q] [-s name | -z zone] -a alg: algorithm (default hmac-sha256) -k keyname: name of the key as it will be used in named.conf -r randomfile: source of random data (use "keyboard" for key timing) -s name: domain name to be updated using the created key -z zone: name of the zone as it will be used in named.conf -q: quiet mode: print the key, with no explanatory text failed to allocate memory for keyname# To activate this key, place the following in named.conf, and # in a separate keyfile on the system or systems from which nsupdate # will be run:key "%s" { algorithm %s; secret "%.*s"; }; # Then, in the "zone" statement for the zone containing the # name "%s", place an "update-policy" statement # like this one, adjusted as needed for your preferred permissions: update-policy { grant %s name %s ANY; }; # Then, in the "zone" definition statement for "%s", # place an "update-policy" statement like this one, adjusted as # needed for your preferred permissions: update-policy { grant %s zonesub ANY; }; # Then, in the "zone" statement for each zone you wish to dynamically # update, place an "update-policy" statement granting update permission # to this key. For example, the following statement grants this key # permission to update any name within the zone: update-policy { grant %s zonesub ANY; }; # After the keyfile has been placed, the following command will # execute nsupdate using this key: nsupdate -k ddns-keyddns-confgenUnsupported algorithm '%s'%s: invalid argument -%c %s: unhandled option -%c a:hk:Mmr:qs:Vy:z:create memory context%s: %s./ddns-confgen.c%s.%s========================================s===fUD=====3%s: hmac-md5hmac-sha1hmac-sha224hmac-sha256hmac-sha384hmac-sha512(unknown)unsupported algorithm %d create entropy contextkeyboardstart entropy sourceinitialize dst librarygenerate keydump key to bufferbsse64 encode secretcreate keyfileunable to set file owner write to %s failed fclose(%s) failed wrote key file "%s" tSSS|lkeysize %d out of range (must be 1-512) keysize %d out of range (must be 1-256) ;TT0DPd$(<`zR|  0F J tx?;*2$"@  & 6 F V f v   & 6 F V f v &6FVf`Ap@@@.shstrtab.interp.note.ABI-tag.note.gnu.build-id.gnu.hash.dynsym.dynstr.gnu.version.gnu.version_r.rel.dyn.rel.plt.init.text.fini.rodata.eh_frame_hdr.eh_frame.ctors.dtors.jcr.dynamic.got.data.bss TThh !$4oL> FNo  t[o j   ps  8 | .w pp@@ ))))H > .(>(.0>0.4>4.$?$/@0 @0D 0