The length was extended to 128 characters in 2.4.0. I'm closing it.

Hi Alexei, are you sure about the 128 characters in 2.4.0?

I have 2.4.0 server and agent and I received the error:
Value "XXXX" is too long for field "dns" - 66 characters. Allowed length is 64 characters.

You probably got confused with the 'host' field that have 128 chars limit now. I found the limits and change it manually, the limits are in:

Here: frontends/php/include/schema.inc.php:971
Here: web/include/views/administration.proxy.edit.php:65
And here at table interface the field DNS is a VARCHAR(64). I updated to 128 with: alter table 'interface' modify 'dns' VARCHAR(128) NOT NULL DEFAULT '';

I didnt found a way to send a "pull-request" of it, if there is a way please let me know! Regards

indeed, host name/ip field in the interface table is still limited to 64 - reopening

Pedro, you can just attach a patch here, but most likely it's not just a frontend thing.

Yup it's also a limit in the database schema

Patch for 128 char support for 2.4 trunk

DB migration patch

OK, it seems to work on one of my servers for a week now, any chance it will come in 2.4.3 ?

There is a policy that Zabbix database schema does not change in minor versions, so versions 2.4.x will not have this change implemented.

Dang. I just noticed that this didn't make it into 3.0 either.

When could this be implemented. The RFC1123 states that 63 characters are the minimum hostname-length a device must support and 255 characters should support. We are using the Zabbix-Repo and don't build it on our own to implement the patch, so we rely on the general avaibility.

I believe the patch does not work as of 3.0.8 (either server or frontend-php version). 3.0.7 seems to be working.

A mirage, because the database field is still varchar(64).

Has this been implemented yet? If not, why/how so? It's been open for quite literally years...

We just ran into this problem too. Seems odd that they would let this be 'out of spec' for so long.

It will be implemented in Zabbix 4.0 if everything goes well.

I think API also has same limit regardless database.

Implemented in 4.0.0alpha1(trunk) r75385.