Yes IPv6 host
addresses can be assigned by DHCPv6,
or self-assigned - based on the MAC address, or something more random if using Privacy Extensions
As I understand it, the LAN interface prefix is usually based on what was provided to the router from upstream (the ISP).
If the ISP provides a /64 that is one network and will be the LAN prefix.
If the ISP provides a /56 or a /48 that can be several subnetted networks so the LAN prefix can be a /64 taken from somewhere in that range, or on a router with multiple real interfaces (not the built-in switch), there can be another prefix used for the DMZ network.
So for the full address for the AAAA record, DHCPv6 reservation or based on MAC address will both give a fixed address (while with this ISP). Don't try to set a host IPv6 address by hand on the server itself (unless setting an address on a router interface), it is not worth the trouble when you'll have to set several long fields up exactly correctly, and you would still have to ensure the router knows about it not to hand out the same address to something else.
The protocols (including DHCP) exist to automate this.
And instead of NAT port forwarding
from destination ports on the WAN IP of the router, one more directly configures the router firewall
to allow requests to reach those ports at the actual destination (server). If the server itself is running a firewall the traffic needs to be allowed there as usual.
So for the sake of other readers in other words the AAAA record will be for a LAN address (or DMZ address if you have one) of the server and not the WAN address of the router as with IPv4 NAT and single public IP.
prompt $P - Invalid drive specification - Abort, Retry, Fail? $G
prlzx on iDNET: ADSL2+ / 21CN at ~4Mbps / 700kbps with IP4/6
Edited by prlzx (Wed 26-Jun-13 20:51:45)