> From: Brian Hatch [mailto:[EMAIL PROTECTED] > I hate to muck with a DNS server to fix this problem. > And since I prefer DJBDNS, a BIND patch wouldn't do > me any good anyway.
At least a BIND patch could be useful for ISP's running BIND or even be reused in DJBDNS and similar. > Is it always returning the same IP address, or have > any other noticable characteristics? If so I'd think > we could set up a firewall rule to drop all DNS > replies that contain the Verisign-be-damned IP address. > That'd protect everything, regardless of name server or > method of access (using host/nslookup/etc manually.) For now, it is returning the same IP address, but I have no trouble imagining Verisign evading DNS filters by changing the A records every now and then. Any solution to prevent Verisigns greed should keep this in mind. Dropping DNS replies would just result in repeated DNS queries, changing the reply to NXDOMAIN as it originally would have been would be better. Regards Thor Larholm PivX Solutions, LLC - Senior Security Researcher http://www.pivx.com/larholm/unpatched - Unpatched IE vulnerabilities _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
