Bug in parsing SNMP host and domain

I'm not sure if this is a server bug or an agent bug...

In 2.1.1 I am seeing the wrong value in the database for NAME in the SNMP table. It looks like the server may be appending the domain of the server to the hostname rather than the domain that the client host should be in.

As an example, here is one of my hosts in the hardware table:
+--------------------------------+------------+-----------+------------+----------------------------------+
| deviceid | name | workgroup | userdomain | useragent |
+--------------------------------+------------+-----------+------------+----------------------------------+
| xlimegecko-2014-05-12-17-01-01 | xlimegecko | pdi.com | NULL | OCS-NG_unified_unix_agent_v2.1.1 |
+--------------------------------+------------+-----------+------------+----------------------------------+

and here is the same host from the snmp table:
+--------------------------------+-----------------------------------------------------------------------------------------------------------+--------------+
| name | description | location |
+--------------------------------+-----------------------------------------------------------------------------------------------------------+--------------+
| xlimegecko.anim.dreamworks.com | Linux xlimegecko.anim.dreamworks.com 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Feb 20 12:17:37 EST 2013 x86_64 | Glendale, CA |
+--------------------------------+-----------------------------------------------------------------------------------------------------------+--------------+

The odd thing is that the location is also wrong, snmp is reporting "Redwood City, CA" for this host:
drich@ocsinventory|1492> snmpwalk -v2c -c public xlimegecko sysName sysLocation
SNMPv2-MIB::sysName.0 = STRING: xlimegecko
drich@ocsinventory|1493> snmpwalk -v2c -c public xlimegecko sysLocation
SNMPv2-MIB::sysLocation.0 = STRING: Redwood City, CA

How is it creating the fqdn for the host in the snmp table? Does that happen on the server or does the client doing the snmp discovery set that data?