So again, at what point do we stop adding code to net-snmp because ISP's are messing around as if they're doing us a favor by letting us use their services?
Thanks, Keith Thanks, Keith On Wed, Apr 4, 2018 at 7:13 PM, Bart Van Assche <bvanass...@acm.org> wrote: > On 04/04/18 09:30, Keith Mendoza wrote: >> >> I actually found no.such.address in line 79 of T070com2sec_simple. >> That host has been hijacked by barefruit.co.uk who "generates highly >> targeted traffic for ISPs by replacing DNS and HTTP errors with >> relevant advertising"; which is now causing the test case to fail. >> Attempting to talk HTTP to the IP gave the the impression that either >> my ISP is cahoots with this company; or they're intercepting the IP >> back to their advertisement page. On the upside, Google's and >> cloudflare's DNS are not resolving; but, that still means point your >> network to use those nameservers :( > > > That means that your ISP is doing something dubious. Anyway, we could add a > workaround for broken ISP DNS configurations using the same approach as for > the domain names onea.net-snmp.org and twoa.net-snmp.org. > > Bart. ------------------------------------------------------------------------------ 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
