DNS Morons

These people should run Split-horizon DNS;

HostWrong IP addressReason
dns2.speednet-wireless.net64:ff9b::ba41:581eRFC 6052
mitvrh.com10.10.10.10RFC 1918
ns.telenettv.ru192.168.128.197RFC 1918
ns1.comeconnect.com64:ff9b::caa4:2051RFC 6052
ns1.netplus.co.in64:ff9b::6729:17c2RFC 6052
ns2.comeconnect.com64:ff9b::caa4:2052RFC 6052
ns2.netplus.co.in64:ff9b::6729:17c3RFC 6052
ns3.tataidc.co.in64:ff9b::6708:2d05RFC 6052
ns4.tataidc.co.in64:ff9b::6708:2e05RFC 6052
ns5.tataidc.co.in64:ff9b::6708:2c05RFC 6052
nssc.scratchspace.com192.168.218.10RFC 1918

Last update: Sat 24 Aug 06:02:01 UTC 2019

Block

You can block answers like these with Bind's 'deny-answer-addresses' feature;

    deny-answer-addresses {
        // Unconfigured
        0.0.0.0;
        // RFC 1918
        10.0.0.0/8;
        172.16.0.0/12;
        192.168.0.0/16;
        // RFC 3927
        169.254.0.0/16;
        // IPv6
        // :: to ::ffff:ffff:ffff.
        // Includes ::, ::1, IPv4-Compatible IPv6 Addresses ::/96,
        // and IPv4-mapped IPv6 addresses ::ffff:0:0/96
        ::/80;
        // RFC 6052
        64:ff9b::/96;
        // Reserved for Documentation
        2001:db8::/32;
        // IPv6 Unique Local
        fc00::/7;
        // IPv6 Link local
        fe80::/10;
        // IPv6 Site local
        fec0::/10;
        // Your IPv6 address range(s)
        Net/Mask
    } except-from { "Your.Domain"; };
    deny-answer-aliases { "Your.Domain"; };

The produces log entries like;

  Aug 21 19:31:01 sput named[1601]: answer address 10.0.0.100 denied for spacefon.com/A/IN

Not blocking these addresses can be a serious security risk.