Closed nerdalertdk closed 10 months ago
You need to modify snmptrap container and allow IP resolving. Remove "-n" option.
Nice thank you :)
any reason it’s off as default ? Performance?
usually is not required. Also sometimes DNS in docker container is not properly configured. What is in your case?
We generally try to use DNS when we can, but after we moved from an old ass 4.2 old school style installation to docker. Traps stopped working. did not consider someone would turn off DNS resolving we are using your DockerFile's, since I maintain enough already 😅 But I'll just make one for the trap service
Actually you can continue to use 4.2 version. There is no difference in output format. Also if you want DNS instead of IP in new versions, please tell us what current traps you receive. Feel free to hide real IP with placeholders, but we need a few ones from snmptrap.log.
Hello!
We have modified snmptraps image (currently only for 6.4 and trunk branches). Now you can use DNS instead of IP address. Please refer to SNMP traps updated documentation.
Fixed!
SUMMARY
Snmptrap docker image can't find host if "Connect to" is set to DNS in Zabbix
When set to IP, it works
OS / ENVIRONMENT / Used docker-compose files
Host: Debian 11 docker: Docker version 20.10.21 Zabbix: 6.2
Snmptrap log
CONFIGURATION
.env_srv