I believe this may be related to the following error messages I have:

@beamerblvd While slightly tangential, I would like to point out that regardless of your opinion of "traditional" NAT, (single external IP, multiple internal IP) NPTv6 makes a LOT of sense for anyone that wants to host services like DNS or web (even just internally) but is on an ISP that doesn't offer static prefixes. It has no issues that I'm aware of past the slight complication of configuration for a network admin, everything good about IPv6 still works with it. (Like the privacy extensions)

@carl.byington It works for incoming response packets, but nothing on the outside can initiate connections as far as I'm aware. Hence, my webserver would be inaccessible.

@carl.byington Works great for outgoing connections, but isn't sufficient for hosting services behind a VyOS router from what I understand, as it needs to request the prefix over DHCPv6-PD for my gateway to know to route incoming packets to it.

This is definitely very important. I'm on AT&T UVerse, and I can't plausibly use VyOS for my network without support for DHCPv6-PD. I don't even need auto-configuration of RAs on the LAN ports if that would be difficult, but I at least need the support to request the prefixes in order to get them routed to my internal router.