I should also note, there is nothing in the logs of the switch saying dhcp_snooping is blocking anything. Also once the access ports the AP's are on were trusted, they were able to get their normal dhcp reservation.

Also this is configured on your trunk ports leading to the DHCP server? I run DHCP snooping in over 50 locations with DHCP enabled AP's and do not have any issues. Are you using a controller? If so what model? Do you have any ACL's?

Port Vlans in spanning tree forwarding state and not prunedGi1/0/1 1-15,26-27,33,100-101,254,301,308-309,319,327,399,700,720,820,888-889,900,999

show vlan br (only showing the LWAP vlan)

===============

100 V100-LWAP active Fa2/0/39, Fa2/0/40, Fa2/0/41, Fa2/0/42,

Fa2/0/43, Fa2/0/44, Fa2/0/45, Fa2/0/46

Basically we have a 5508 controller connected to our 6500 core. Turned on DHCP snooping. Upgraded Controller code and ap code. When the controller and AP's rebooted they were unable to get their DHCP reservations. Added the AP access ports as trusted ports like the above example f2/0/44 and then they got their dhcp reservations.

My setup is very similar. My 5508's are plugged into my core 6500, but I am not running dhcp snooping on my core, because my AP's are not plugged into that device. Take a look at my diagram. Its not very complicated at all. See if it helps. Otherwise I would need some more specifics to lab it up at my desk and see if I can replicate the problem