Author(s):	Robert Mibus
Location	C001
Date	jan Tue 17	Days Raw Files
Start	14:20	First Raw Start	error-in-template
Duration	0:50:00	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2012.linux.org.au/schedule/168/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf IPv6_Dynamic_Reverse_Mapping_the_magic_misery_and_mayhem.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	We all want IPv6, because the sky is falling, and many of us have gone back to the future and are trialling IPv6 already. This is a good thing. But many of us want our NodePonies too - we want those v6 addresses reverse mapped. There's no way your ISP is going to handle all those reverse mappings manually like they did for v4 - there's around 2^72 entries per customer! What do you use to solve your problem - use pymds! This presentation is a real-world case study of how a successful Australian ISP - Internode - took a simple open-source DNS server and made it part of their production DNS environment. As we fall down the rabbit hole we'll discuss: * Why people want all IPv6 addresses to have reverse mappings * Solutions that were ruled out (eg. BIND's "GENERATE" macro) * Why pymds was picked (ie., rapid prototyping is better than weeks of effort). * Naming/formatting options we went through for what the reverses should look like * Options for integrating it into our main DNS zones. * How can we easily override the automatic generation, without complicating the codebase. * Pitfalls we expect to see * Future evolution possibilities, competing projects [Note: Our modifications to pymds are not yet available publicly, but will be by the conference - promise! We know that's not ideal, but our legion of code ponies are busily cleaning up the source before releasing - internal approval to release has already been granted] Appropriate for Sysadmins, advanced users, and people playing with IPv6 in their basement. markdown
Comment:	production notes