@David-TP 

I think that, as broadly described in the "Separate DNS settings for guest network" topic, there is a very good use case for this.

Guest Network is designed for seperating Guest from regular traffic. When the internal, trusted network uses a own local DNS-server, the Guest network is rendered usuable, as the DNS server is not accessible.

It would be highly appreciated if this could be fixed.

  @David-TP I would very much like to see a robust WebUI and separate DNS settings for the Guest and Main networks. 

  @David-TP I would like to have separate DNS settings for the guest network. On the main network I have my own DNS running for blocking content for one reason or another. Devices on the guest network do not have the ability to access that, so it would be a big win to allow those devices to have their own settings. 

  @David-TP please consider the separate DNS configuration for guest networks

  @David-TP +1 for the separate DNS settings.

  @David-TP 

I'm also going to +1 the DNS request, but broaden the scope a bit and say that it must include a complete DHCP scope for the guest VLAN. I explaned why a bit in my response (post #62) to the main topic, but in brief if you are going to have a deicsion tree that assigns different DNS based on the inbound DHCP request souce then there is no good reason you can't also let that decision tree include different subnets.