EddieZ: My last post was a response to your assertion that having the built in DHCP server only respond to requests in the guest zone was technically infeasible based on the architecture of the router. This is what doesn't make sense to me. The importance of said feature is a separate matter.
As for whether the feature belongs in this "router class", I would first say that features vary greatly between routers. One of the main reasons that I picked this router was that it supported various "advanced" features that it's competitors do not, such as WPA Enterprise authentication. I have also read about other people who wanted this exact feature in a home router, so I don't think it is weird or unusual in any way.
Now, if there is a good technical reason why having the DHCP server respond to only one network is infeasible (or, equivalently, blocking traffic between the other and the DHCP server), please let me know, but your previous explanation did not jive with my previous networking experience. Would you be able to describe why separate radios would be required in more detail? Changing which of the internal VLAN(s) the internal DHCP server binds to would seem to me to be a fairly trivial matter.
I am not trying to be a pain, I just like to understand what is going on.
ttmcmurry: DHCP relay is not at all what I am looking for, and I agree that that would be a feature beyond the scope of this router. I do not what the guest network to obtain addresses from the standalone DHCP, and indeed, I want the networks to be isolated from each other. I am trying to have the guest network be served by the routers built in DHCP server, like it normally is, but at the same time be able to use my standalone DHCP server on the main network.
Thank you all,
Erik Jensen