I’ve managed to get IPv6 running on my network and routing (with firewall, of course) to the world. I’ve got a /56 from my provider. I’m a fairly happy camper. I can add the AAAA records to my bind9 server without issues, but they don’t stay static, of course.
The issue I want to resolve is addresses being self-assigned means my own systems are hard to track, manage with queues, FW rules and, of course, names. What seems like the best approach is to move to static IPv6 addresses with ISC-DHCP for manageability. The issue I’m having is on how to configure ISC-DHCP with respects to my Mikrotik. Does anyone here have experience in getting ISC-DHCP(v6) working with a Mikrotik as the WAN interface + getting a ::/56 (or ::/64 for that matter) pool?
Conversely, am I just going about it in to much of a IPv4 mindset and is there a better way?
External DHCPv6 server is generally fine, I use RouterOS as gateway and Dibbler on another machine for many years. Unlike in IPv4 world, where DHCP assigns both address and default gateway, DHCPv6 assigns only address and gateway comes from Router Advertisements. So you just set M and O flags (managed addresses and other config for DNS) in “/ipv6 nd”, then configure used prefix (and other options you need) on external DHCPv6 server and you’re done.
If your /56 is fully static, you don’t need anything else. If it comes from ISP’s DHCPv6, you’ll have to find a way how to pass it to your other DHCPv6 server. I didn’t test it, but you should be able to set up DHCPv6 PD server on RouterOS (it can take prefixes from pool filled by DHCPv6 client on WAN), then client on the other machine and it should be able to pass it to server.