Update:
The IAP 3.4 fix committed merely makes it so that APs on 3.4 that DHCP don't pre-fill domain with foo.com.
On the AirWave side, if you have a new IAP that's already on 3.4, then domain name will be empty / null. But if you already had the AP monitored / managed in AirWave before upgrading to 3.4, then you'll need to perform an import settings on the AP.
Steps to update individual AP:
1. Navigate to IAP (AP entry, not VC)
2. Go to manage page
3. Select 'import settings' at the bottom right
4. Confirm
5. Wait a few minutes, then the foo.com should be gone
Steps to update bulk APs:
1. Navigate to a group or folder view (if folder view, you can expand top and then filter for just the non VC devices
2. Select the 'modify devices' wrench above the list table (checkboxes will appear next to devices)
3. Check all devices that are currently showing foo.com as domain
4. Below the list table -> find and select 'import settings'
5. Confirm
6. Wait a few minutes, then the foo.com should be gone