now I've got a question

I'm helping this guy setup his dns server, but there's a problem. His IP is dynamic. So I offered to be the target of his registrar NS entries. All my server would do is redirect the dns client to query his dynamically updated IP domain for dns information reguarding his zones. Basically I want it to be like this:

DNS Client queries a.root-servers.net for www.foo.net
A.ROOT-SERVERS.NET responds with A.GTLD-SERVERS.NET

DNS Client queries A.GTLD-SERVERS.NET for www.foo.net
A.GTLD-SERVERS.NET responds with ns.myserver.com (me)

DNS Client queries ns.myserver.com for www.foo.net
ns.myserver.com responds with dynamic.dns.com

DNS Client queries dynamic.dns.com for www.foo.net
dynamic.dns.com responds with 127.0.0.1

I want my server to be just another step in the resolving process. However, I can't seem to do it. I thought all I had to do was the following:

[named.conf]
zone "foo.net" IN {
type master;
file "foo.net.zone";
}

[foo.net.zone]
foo.net. 900 NS dynamic.dns.com

Just that one line should've been all I needed. Without the SOA record the zone would not be authoritative, and the NS would provide redirection. However, BIND complains that there isn't any SOA records and returns servfails for all requests to foo.net. When I add the SOA record my server returns authoritative for any queries reguarding the foo.net zone.

How should I fix this?

So many questions answered but not mine?

hmm, It has been my experience that DNS Servers without statically assigned IP's are destin for punishment from every angle.
This could be possible if this was a subdomain delegated or a stub, but then again, you often have issues with glue records due to the A record changes and your NS does not resolve anymore. Therefore breaking the delegation from the parent domain. You know I will be pondering this in my sleep tonight now,, Are you good at scripting? You might be able to create a script to manually edit the zone file everytime his ip changes and rndc reconfig zone.com to take the change? That might be the simplest approach?

Cheers

that's what I'm doing right now. I've already created a small program to update the zone. I've also created a web based form for him to manually edit his zone where the changes take effect immediately. Currently I'm working on a dynamic IP client that he can use to update his zone directly and get rid of the dynamic IP service he currently uses.

But I am still curious as to how I can provide dns server redirection. There is one solution you know. I can create a .net or .com zone and delegate his domain. That's how the root and gtld servers do it. But my server also performs as a caching server so that would mess up my resolution of .com or .net domains.

Perhaps there is no other way.

P.S. if you have any dns related issues/questions concerning server/protocol or standards I'd be glad to answer. I used to flood the board with answers like you're doing until I got burned out.

Hey thanks SilentRage for the offer. I try to help out when I can.
I will keep my eyes open regarding your "research".

Cheers,
Mike