I'm not sure, I'm getting you right. Do you want to set up a subdomain for a registered domain in a way, that the subdomain is managed under a different zone?
If yes: you need to know nothing about resolv.conf, your DNS resolver takes care of all that. Just make sure, the resolver knows about your domain. (If you have officially registered it, this is allready the case.)
Let's take example.com az a zone, ns1.provider.com and ns2.provider.com as NS servers and 1.2.3.4 as the IP address of your NS server for the subdomain. Your zone file for example.com. would look like this:
Code:
$TTL 600
example.com. IN SOA ns1.provider.com. hostmaster.provider.com. (
2009102601
86400
7200
604800
600 )
example.com. IN NS ns1.provider.com.
example.com. IN NS ns2.provider.com.
example.com. IN A 1.3.5.7
example.com. IN MX 5 mx.provider.com
home.example.com. IN NS ns.home.example.com.
ns.home.example.com. IN A 1.2.3.4
Note the last line. This is called a glue record. Without this, the recursor has no way of resolving ns.home.example.com. If you have done this correctly, you should now be able to create a new zone called home.example.com in your DNS server at 1.2.3.4 with all the glory and pain of a grown-up zone.
If should look like this:
Code:
$TTL 600
home.example.com. IN SOA ns.home.example.com. me.example.com (
2009102601
86400
7200
604800
600 )
home.example.com. IN NS ns.home.example.com.
ns.home.example.com. IN A 1.2.3.4
home.example.com. IN A 1.2.3.4
I hope this helps. If you try it out, please try on a domain you don't care about. Messing with the DNS can easily result in your e-mail or website not working. You have been warned.