VLAN Tagging on Trunk Port

As Adam stated, generally in a well designed network, you should not be receiving untagged frames on a trunk port. Based on your description, you only want and expect to send and receive VLAN 24 on the uplink port. Thus, configure the port as an access port in VLAN 24:

interface gig0/1
 switchport access vlan 24

If for whatever reason this needs to remain a trunk port, but you still only want VLAN 24 (untagged), then configure as a trunk, but set the native VLAN to 24:

interface gig0/1
 switchport trunk encapsulation dot1q  !may not be necessary depending on hardware
 switchport mode trunk
 switchport trunk native vlan 24

Basics

When you tag a VLAN on a port, it will send out the traffic on that port with the VLAN tag, when the port receives traffic it looks for the tag and places the traffic into that VLAN. You can have multiple tagged VLANs on one port (sometimes called trunk).

When you send out a VLAN untagged on a port it will not add the VLAN tag to the packet and when receiving packets without a VLAN tag it will be placed into that VLAN (on Netgear and others you have to set PVID (Primary VLAN ID))

To your problem

I think you are not far away... - Router port connected to Switch1 should have IP within VLAN 2220. - DHCP Server should have different IP from different Subnet! - Router port Connected to Switch2 should have IP in Subnet of DHCP Server - You should define a DHCP Helper on Router port connected to Switch1 so DHCP Request get forwarded to DHCP Server. Hot to do that is described here: http://kb.netgear.com/app/answers/detail/a_id/21990/~/how-do-i-configure-a-dhcp-l3-relay-using-the-web-interface-on-my-managed-switch%3F

Hope this helps you a little bit further. If not, please post a more detailed network diagram with VLAN IDs and IPs.