You won't (at least not as far as I know) Reverse checking is ONLY a concern for the following protocols: * SMTP * SSH Everything else more or less does not care about it. It is good practice to make sure that hosts have a reverse. But for instance in the case of IPv6 Privacy Addresses, where the address is more or less randomly generated it is actually a goal not to do that in the first place, next to it being unfeasible. As such, for hosts that speak SMTP outside of your organization: make sure they have proper RDNS setup, as SMTP servers will reject clients they don't know and don't have a proper reverse+forward combination. For SSH it is a convenience factor as the hostnames look nice and are easier to remember than IP addresses. (still if you only store hostnames, then the mapping from IP->name->IP can change and you lose quite some value in tracking down what host it really was...) If you want to automate it, either use DDNS (Dynamic DNS) or indeed DHCPv6. Other option, if you are a Windows shop, is to let Active Directory take care of it.