I wouldn't bet on any changes. This is a home class router, segregated DHCP/DNS services don't usually fall in this class of router.
I was afraid of that. I like the Cisco and Sonicwall and Watchguards etc...but they are out of my price range. Reviews show this to be one of if not the best home class wifi router on the market. When I realized this did a Guest wifi I got really excited....until I realized that by running my own DHCP server and DNS server on a Server 2008 box thats connected to the LAN....my GuestWifi was receiving invalid settings since they couldn't communicate with the DNS server after receiving an IP via DHCP. Further thinking made my wonder why the DHCP server even handed out an IP...given the guest accounts shouldn't even be able to communicate with the LAN zone....
EDIT: So I've enabled DNS relay on the router. I've modified the DHCP scope on my server 2008 box to hand out two DNS servers, itself as the primary, and the router's IP as the secondary. This way the LAN and WiFi clients use the server 2008 as the primary, and the router for backup. The Guest wifi clients have the server as primary, which never responds to DNS responses, and the router as the backup, which works fine. Not the ideal situation, but it works.