A> We have a customer who has recently registered one of these new
A> .name domains with Verisign (NetSol), and now want us to host
A> their site and email for them. [...]
A> [...] how should we configure our DNS?
You say that your customer wants you to provide its HTTP content service
and SMTP Relay service. However, you don't say that your customer wants
you to provide its DNS content service.
If your customer doesn't want you to provide its DNS content service,
then you don't need to do _anything_ to your DNS servers at all. The
only servers that you need be concerned with are your HTTP content
servers and your SMTP Relay servers, both of which should be told (in
whatever way is appropriate for your choice of softwares) that they are
to provide their respective services for your customer's domain, in
addition to what domains they already provide service for. This
reconfiguration of those servers has nothing to do with the DNS.
If your customer actually does want you to provide its DNS content
service, then all that you do is create an appropriate "forward lookup"
"zone", the same as you have already done for all of the other "zone"s
that your DNS content services already serve.
If your customer owns "bloggs.name.", then it has (and thus you have,
assuming that it wants you to provide its DNS content service for it)
the power to determine what the SMTP Relay server for "bloggs.name." is,
are routed. If, however, your customer only owns "fred.bloggs.name.",
then neither it nor you have the power to determine what the SMTP Relay
server for "bloggs.name." is. That power belongs to the owner(s) of