In message <4DF91AB3.6020107@mompl.net>, Jeroen van Aart writes:
Leo Bicknell wrote:
but it all doesn't matter because the network team hadn't actually made IPv6 work yet as there was no business case.
Ahhh, ok, well at least I know I did it right the first time.
No, I'm not cynical. :)
It probably reflects daily practice for many big organisations, sadly. Luckily I can configure dns, firewall/routing and (ipv6) networking myself, so no need of passing along spreadsheets (besides I really hate spreadsheets).
Seth Mattinen wrote:
I can send you a copy of my config offlist if you'd like; there's really nothing to it and it's been going along fine for as long as I can
That won't be necessary, thanks. I think I have configured it correctly and created the correct IPv6 records. Just wanted to make sure.
Greetings, Jeroen
-- http://goldmark.org/jeff/stupid-disclaimers/ http://linuxmafia.com/~rick/faq/plural-of-virus.html
You tell named to listen on IPv6 (listen-on-v6). It already uses IPv6 to make queries unless you turned it off on the command line with "named -4". To go IPv6 only on a dual stack machine use "named -6". You add AAAA records to the zones for the nameservers. You update your glue records in the parent zone to include AAAA records as well as A records. You add IPv6 address to resolv.conf or equivalent (DHCPv6, the new RA option). You can mark non-local ula's as bogus and your one local ulas as good in named.conf. servers fc00::/7 { bogus yes; }; servers fdxx:xxxx:xxxx::/48 { bogus no; }; If you are only using IPv6 internally servers ::/0 { bogus yes; }; servers <internal-range> { bogus no; }; You should also be doing this at the routing level. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org