We are using NET-SNMP version: 5.7.3 to setup a snmp proxy.
Everything is fine except that if the dns server is not available at
snmpd startup, remotehost names are not resolved and the queries fail.
We tested that name to ip translation is made at startup. No matter if
it is via DNS or even /etc/hosts.
The config is:
proxy -Cn ctx_remotehost1 -v 1 -c community switch.sub.dom r .1.3
if switch.sub.dom is in /etc/hosts or resolved via DNS during snmpd
startup it works OK.
BUT if name is not present (hosts or DNS) at startup and added later
it's not checked again when a snmp query is received.
This leads to problems if local equipment startup is in wrong order
(dns after snmpd).
Other scenario with the same problem is if the IP/name mapping changes
with snmpd running, Either because of /etc/host edit or dynamic IP
assignment in DNS.
It keeps proxying to the original IP address.
There is any flag to force dns resolution in each query? or other option?
or it is a design decision (or bug).
Thanks in advance!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
