For some reason, I'm getting Windows systems where the hostname is sometimes in upper case, sometimes not. It would be nice if autoregistration had a way to handle that. (Or I'm not seeing it)
-
-
"The Internet standards (Request for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. However, a subsequent specification (RFC 1123) permitted hostname labels to start with digits. No other symbols, punctuation characters, or white space are permitted."
So from RFCs point of view case sensitiveness in this case is lack of compliance with RFCs. So seems it is kind of bug
http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
https://kloczek.wordpress.com/
zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
My zabbix templates https://github.com/kloczek/zabbix-templates -
Yes, but Zabbix doesn't FORCE you to use the DNS name for the hostname does it? For some reason, our Windoze boxes are only returning the host part of their dns, dropping the domain, but it makes my screens easier to navigate, so I'm not griping.
I'll report it as a bug and see where it goes :-)Comment
Comment