;; ADDITIONAL SECTION:a.nic.de. 2191 IN A 194.0.0.53a.nic.de. 2191 IN AAAA 2001:678:2::53c.de.net. 2191 IN A 208.48.81.43f.nic.de. 2191 IN A 81.91.164.5f.nic.de. 2191 IN AAAA 2001:608:6:6::10l.de.net. 2191 IN A 77.67.63.105l.de.net. 2191 IN AAAA 2001:668:1f:11::105s.de.net. 2191 IN A 195.243.137.26z.nic.de. 2191 IN A 194.246.96.1

May112010

Pokemon Exception Handling

May082010

September092009

09:04

wtf / fun with bind

with "listen-on-v6 { any; };" my bind9 instance binds correctly to all Ipv6 addresses. But as this is bad style - one does not bind services to all Ips, especially not a DNS server - and as it would even cause problems - I have a dnscache on ::1, bind9 is only authoritative - I want it to bind on a specific address. A "listen-on-v6 { 2001:123:1234::1/128; };" should do that. Hrm, after a restart of bind it does not listen on IPv6 at all.I start up named with "named -g -d 5 -c /etc/bind/named.conf -u bind" for debugging. Here, bind9 binds nicely on the v6 address. So what is that initscript in debian doing different? Hrm, obviously it uses "-t /var/lib/bind" to chroot the named, which is probably a good idea as bind is relatively complex. But that can't have anything todo with IPv6, can it? Firing up "named -g -d 5 -c /etc/bind/named.conf -u bind -t /var/lib/bind" I was negatively stunned: It does have something todo with IPv6. There is no error message or something, it just does not bind on IPv6. For what reason, I can only guess.