gary_alderson on Nostr: see how many of these points are valid/salient/pragmatic or interesting good ...

see how many of these points are valid/salient/pragmatic or interesting
good background info, it is a bit of a rabbit hole #dual stack dns

The "Get It Done" IPv6 Checklist

Phase 1: Preparation & Verification

Verify Verizon Eligibility: Confirm your specific Verizon Business account (with static IPv4) actually supports DHCPv6 Prefix Delegation (PD). Check your account portal or contact support, as some static IPv4 accounts are not yet eligible for IPv6.

Confirm Delegated Prefix Size: Find out if Verizon is delegating a /56 or just a /64. You need a /56 to split into multiple subnets for your different segments.

Phase 2: MikroTik Core Configuration

Configure DHCPv6 Client on WAN: Set up a DHCPv6 client on your WAN interface. Crucially, set prefix-hint=::/56 to request the larger block.

Stabilize the DUID: Configure your MikroTik to use a stable DUID-LL (based on the MAC address), not DUID-LLT (which includes a timestamp). This prevents Verizon from assigning a new prefix every time the router reboots.

Create a Dynamic IPv6 Pool: The DHCPv6 client will automatically create a dynamic pool from the delegated prefix it receives. Ensure this is active.

Assign Subnets to Segments (VLANs): For each of your segmented interfaces (VLANs), assign an IPv6 address using from-pool=<pool-name> and prefix-length=64. The first VLAN gets ::/64, the second gets ::1/64, and so on.

Enable Router Advertisements (RA): On each segmented interface, enable Neighbor Discovery (ND) with the "Advertise" flag so clients can autoconfigure (SLAAC) with addresses from the correct subnet.

Phase 3: Firewall & Segmentation

Implement Firewall Rules: Add IPv6 firewall rules on the MikroTik to manage traffic flow between your segmented networks, just as you would with IPv4.

Phase 4: Service Stability & DNS

Adopt ULAs for Internal Services: Assign static Unique Local Addresses (fd00::/8) to all internal servers and services. This gives you completely stable, predictable IPv6 addresses that will never change, regardless of your ISP's prefix.

Implement DDNS for Public Services: Write a MikroTik script to monitor the delegated prefix. When it changes, the script should automatically update your Dynamic DNS (DDNS) provider with the new AAAA records for any public-facing services.

Phase 5: Long-Term Strategy

Test and Monitor: Observe the prefix stability over a few days. Note how often (if ever) it changes.

Explore a Static IPv6 Upgrade (Optional): If the dynamic nature proves too disruptive and DDNS/ULA isn't sufficient, inquire with Verizon Business about purchasing a dedicated Static IPv6 block (a paid service). This would eliminate the dynamic challenge entirely.