On Wed, 27 Jun 2018 19:54:31 -0300 Nico wrote: N> This leads to problems if local equipment startup is in wrong N> order (dns after snmpd). N> N> Other scenario with the same problem is if the IP/name mapping N> changes with snmpd running, Either because of /etc/host edit or N> dynamic IP assignment in DNS. N> N> It keeps proxying to the original IP address. N> N> There is any flag to force dns resolution in each query? or N> other option? or it is a design decision (or bug).
There is no flag for that. I think it falls somewhere in between a bug and a design decision. The problem with doing DNS every time is that it causes the whole agent to hang if there is a problem with DNS lookups. So I don't think always doing a lookup will ever be the default, but I can see accepting a patch to add a flag for this. If you can code that patch, submit it to the patch tracker. If not, then you could submit a feature request. Robert ------------------------------------------------------------------------------ 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
