forward DNS mapping to another NS address pool

[Jonathan de Boyne Pollard]

rp> I have been given a request to add a forward DNS mapping. 

If you know that the IP address is statically assigned, or if it is
dynamically assigned and you have an agreement with the owner of the service
being named that you will be informed every time that it is scheduled to
change in the future, then just add an "A" resource record to your database
and update that resource record whenever you are notified that the IP address
is scheduled to be changed.  (If the IP address is statically assigned then of
course there is no such ongoing maintenance work for you to do.)

Only if the IP address is dynamically assigned and you are _not_ guaranteed
that you will be informed every time that it is scheduled to change, do you
need to employ client-side aliases.  You publish a "CNAME" resource record
that aliases the domain name to a domain name that is under the aegis of the
same entity that controls the changing of the IP address, and rely on that
entity to keep the mapping from that latter name to the IP address up-to-date.

So the questions that you have to find the answers to are whether the IP
address is statically assigned, and (if it is not) whether you have an
agreement with the owner of the service being named that you will be informed
every time that its IP address is scheduled to change in the future.