Re: AXFR from Bind oddities
Peter Pentchev <[email protected]> Tue, 13 Apr 2010 11:41:07 +0300
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Apr 13, 2010 at 10:25:49AM +0200, Jakob Hirsch wrote: > DAve, 2010-04-12 19:00: > > >> It wouldn't be hard to add a few lines to axfr-get.c to format > >> txt records, but there would be no benefit I can see. > > As I suspected, I didn't fully understand what was going on 8^) > > This is a very unique situation for two client's only, so I will change > > my script to use dig to make the axfr query and Net-DNS-Zonefile to > > parse the result and load VegaDNS. > > Um, why do you care? The output from axfr-get is perfectly suited for > tinydns, so as long as you don't want to manually edit the transferred > zone (which you probably won't), you can use it as-is with tinydns and > spare all the hassle. He seems to be using VegaDNS, a quite simplistic web-based tinydns administration interface. From what I've seen in its source, it cannot handle generic RR (:) lines. G'luck, Peter -- Peter Pentchev [email protected] [email protected] [email protected] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 I am the thought you are now thinking.
signature.asc
(application/pgp-signature, 834 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQIcBAEBCgAGBQJLxC4iAAoJEGUe77AlJ98TxaMP/3hkZuE3kV9H1yrR8TQHCpMS /HKKnLKugGQRioQWUkyBrOOu7TVy3F7WdPirHAQBCmefc16LnWCsieaBetKX8CL0 8M0PY4eS6epukmhBTipWfXfM9ZGqw55hOZUWs5Z6rp5VXlcIXIYdkNWy3K/UVFHz YlT8MEpDM0hrmroVhMOzLP+eZ4aCYPem7YY+nhXc8VSEf4iqKfYuPNFNgz9wPcDB WiavTgqd52E2h/rApbt0KVkJnhfZWzy3l6KH49pJvZAuF0CmBKjAI1FDuqSRxF6y W0CjFos9INDqFn9BQZrQFWj+a9wVF+EPgVfxi8PxU0EP+GGGywTtLnyJKeXdCc9d cntKiGxbxn6IB570w/bYQQlxgj3QZucrpu4lZPjnPAckbRDml320J86m1xxW2iLH WBT7RHmEUnf8cYDq/mcid2xZzWFFquq8xJajgfrEi43BUz6xU56UtVdS+qxs820R 46vjIR92FEMo6dapIHDEBD1wS0Zvjc5ZNSGX8UZahGCpAYamY6VYJq9P+SBpmtyG Ybd9/FIcrWX9LWjChfk0Mv006mTSyl8Ekcs4Oq6zXSFiNDFcNQfDEwV8EbmCDwOJ yJ8g4+GA7gwciL5Q9AZiGumHV+JDNgnv5zXr7IfvMpGkScSU9VDHwMUP6krZH6Zc pLNCT97Ub4BRA7wQOlCe =d9Vx -----END PGP SIGNATURE-----