20 May
2016
20 May
'16
11:15 a.m.
This might be more support-related, but has anyone set up delegated
reverse DNS for IPv6 with "all-knowing-dns"?
It handles PTR and AAAA records on the fly and lets me avoid doing the
whole zone-file thingy. But I'm uncertain about this bit :
"Please bear in mind that the zone
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa should already exist on all the
nameservers you list."
Can I use "all-knowing-dns" as an easy fix?
$ apt-cache show all-knowing-dns
Package: all-knowing-dns
Version: 1.7-1
Installed-Size: 38
Maintainer: Debian Perl Group <pkg-perl-maintainers(a)lists.alioth.debian.org>
Architecture: all
Depends: init-system-helpers (>= 1.11), perl, libmouse-perl,
libmousex-nativetraits-perl, libnet-dns-perl, libnetaddr-ip-perl,
libprivileges-drop-perl
Description-en: tiny DNS server for IPv6 Reverse DNS
AllKnowingDNS provides reverse DNS for IPv6 networks which use SLAAC
(autoconf), e.g. for a /64 network.
.
The problem with IPv6 reverse DNS and traditional nameservers is that the
nameserver requires you to provide a zone file. Assuming you want to
provide
RDNS for a /64 network, you have 2**64 = 18446744073709551616
different usable
IP addresses (a little less if you are using SLAAC). Providing a zone
file for
that, even in a very terse notation, would consume a huge amount of
disk space
and could not possibly be held in the memory of the computers available
nowadays.
.
AllKnowingDNS instead generates PTR and AAAA records on the fly. You only
configure which network you want to serve and what your entries should
look
like.
Description-md5: 1df6f6c08cc7056f9106168642d482b9
Homepage: https://metacpan.org/release/AllKnowingDNS/
Section: perl
Priority: optional
Filename: pool/main/a/all-knowing-dns/all-knowing-dns_1.7-1_all.deb
Size: 22260
MD5sum: 8f70307d17b1690e293595ecd349c436
SHA1: 5c9002dacf99bd5085d8e7ebfdc3f247d8a2287d
SHA256: 712b360eb1830fa175a8b476276979212dd6405987b4c859e5651c377346aac8
20 May
20 May
12:32 p.m.
On fre, 2016-05-20 at 13:15 +0200, Ole-Morten Duesund wrote:
This might be more support-related, but has anyone set
up delegated
reverse DNS for IPv6 with "all-knowing-dns"?
Used to run it at home, for a SixXS range.
But I'm uncertain about this bit :
"Please bear in mind that the zone
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa should already exist on all
the nameservers you list."
Well, you need run an independently configured all-knowing-dns daemon
on each host you delegate your zones to. That is, just having a
designated master/primary server won't do. I would assume that that is
what the quoted text is referring to.
// Andreas
12:54 p.m.
On 20/05/16 14:32, Andreas Olsson wrote:
On fre, 2016-05-20 at 13:15 +0200, Ole-Morten Duesund
wrote:
Ah - of course. So, just configuring all-knowing-dns for my subnet
should work just like magic? It certainly appears to work as expected
when testing it.
- OM
This might be more support-related, but has
anyone set up delegated
reverse DNS for IPv6 with "all-knowing-dns"?
Used to run it at home, for a SixXS range.
But I'm uncertain about this bit :
"Please bear in mind that the zone
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa should already exist on all
the nameservers you list."
Well, you need run an independently configured all-knowing-dns daemon
on each host you delegate your zones to. That is, just having a
designated master/primary server won't do. I would assume that that is
what the quoted text is referring to. 
1:29 p.m.
Hi Ole-Morten,
On Fri, May 20, 2016 at 01:15:01PM +0200, Ole-Morten Duesund wrote:
This might be more support-related, but has anyone set
up delegated
reverse DNS for IPv6 with "all-knowing-dns"?
It handles PTR and AAAA records on the fly and lets me avoid doing
the whole zone-file thingy.
If you are doing static IPv6 configuration, which I would always
recommend, then I don't think there is a point to all-knowing-dns as
it is for answering reverse lookups with a generic/computed
response, and forward lookups for those computed responses.
If using static IPv6 configuration then it seems less work to just
run a normal DNS server.
If you did want to use all-knowing-dns though, you would only
delegate the zone to your single VPS as all-knowing-dns would not be
running elsewhere.
So let's say you run all-knowing-dns on your VPS, vps.glemt.net, and
you tell the panel to delegate reverse DNS for
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa to vps.glemt.net. You also
tell it to generate host names inside v6.glemt.net, so you also have
to delegate v6.glemt.net to vps.glemt.net in whatever nameservers
are authoritative for glemt.net.
So, all that will work and all-knowing-dns will be answering reverse
and forward queries for all IPs inside 2001:ba8:1f1:f2fe::/64.
But my point is, if you are already in the position to be managing
the DNS for glemt.net and can delegate things inside that zone to
other servers, why not add one more zone file and do the static IPv6
DNS?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
1:34 p.m.
On 20/05/16 15:29, Andy Smith wrote:
Hi Ole-Morten,
On Fri, May 20, 2016 at 01:15:01PM +0200, Ole-Morten Duesund wrote:
Fair point, but I'm not actualy doing my own DNS - it's done via my
registrar and I was kind of hoping to keep it that way, but still be
able to get reverse lookups working for IPv6.
- OM
This might be more support-related, but has
anyone set up delegated
reverse DNS for IPv6 with "all-knowing-dns"?
It handles PTR and AAAA records on the fly and lets me avoid doing
the whole zone-file thingy.
If you are doing static IPv6 configuration, which I would always
recommend, then I don't think there is a point to all-knowing-dns as
it is for answering reverse lookups with a generic/computed
response, and forward lookups for those computed responses.
If using static IPv6 configuration then it seems less work to just
run a normal DNS server.
If you did want to use all-knowing-dns though, you would only
delegate the zone to your single VPS as all-knowing-dns would not be
running elsewhere.
So let's say you run all-knowing-dns on your VPS, vps.glemt.net, and
you tell the panel to delegate reverse DNS for
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa to vps.glemt.net. You also
tell it to generate host names inside v6.glemt.net, so you also have
to delegate v6.glemt.net to vps.glemt.net in whatever nameservers
are authoritative for glemt.net.
So, all that will work and all-knowing-dns will be answering reverse
and forward queries for all IPs inside 2001:ba8:1f1:f2fe::/64.
But my point is, if you are already in the position to be managing
the DNS for glemt.net and can delegate things inside that zone to
other servers, why not add one more zone file and do the static IPv6
DNS?
2:45 p.m.
Hello,
On Fri, May 20, 2016 at 02:32:43PM +0200, Andreas Olsson wrote:
On fre, 2016-05-20 at 13:15 +0200, Ole-Morten Duesund
wrote:
Yes, the quoted text is from the BitFolk Panel noting that although
that part is where you tell BitFolk where to delegate the zone to,
you do actually have to have a DNS server running on that host or
hosts, and authoritative for the zone in question.
So in the all-knowing-dns case, you would need to be running it on
each host you delegate the zone to.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
But I'm uncertain about this bit :
"Please bear in mind that the zone
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa should already exist on all
the nameservers you list."
Well, you need run an independently configured all-knowing-dns daemon
on each host you delegate your zones to. That is, just having a
designated master/primary server won't do. I would assume that that is
what the quoted text is referring to.
3:11 p.m.
On 20/05/16 16:45, Andy Smith wrote:
Hello,
On Fri, May 20, 2016 at 02:32:43PM +0200, Andreas Olsson wrote:
Ah - simple misunderstanding then. I thought it
obvious that I'd have to
provide a dns-daemon on all delegated hosts, couldn't figure out
whatever the quote was really about :-)
Thanks!
- OM
On fre, 2016-05-20 at 13:15 +0200, Ole-Morten
Duesund wrote:
Yes, the quoted text is from the BitFolk
Panel noting that although
that part is where you tell BitFolk where to delegate the zone to,
you do actually have to have a DNS server running on that host or
hosts, and authoritative for the zone in question.
So in the all-knowing-dns case, you would need to be running it on
each host you delegate the zone to. But I'm uncertain about this bit :
"Please bear in mind that the zone
e.f.2.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa should already exist on all
the nameservers you list."
Well, you need run an independently configured
all-knowing-dns daemon
on each host you delegate your zones to. That is, just having a
designated master/primary server won't do. I would assume that that is
what the quoted text is referring to.
2907
days inactive
2907
days old
6 comments
3 participants
participants (3)
-
Andreas Olsson -
Andy Smith -
Ole-Morten Duesund