DNS Morons

These people should run Split-horizon DNS;

HostWrong IP addressReason
cache1.clt.hostedsolutions.com10.149.12.23RFC 1918
dns1-410.midco.net10.54.3.12RFC 1918
dns-sna-0102.corp.wayport.net172.17.32.143RFC 1918
gw-ciw.stanford.edu172.26.248.79RFC 1918
gw-ciw.stanford.edu172.26.69.85RFC 1918
hertz.xl.net.id64:ff9b::ca98:fef6RFC 6052
ns0140.netapp.com10.120.60.210RFC 1918
ns040.netapp.com10.64.40.5RFC 1918
ns060.netapp.com10.100.60.210RFC 1918
ns100.netapp.com10.133.254.11RFC 1918
ns1.netplus.co.in64:ff9b::6729:17c2RFC 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
snbdc-dns1.xl.net.id64:ff9b::70d7:25b6RFC 6052
snbdc-dns2.xl.net.id64:ff9b::70d7:25b7RFC 6052
socrates.xl.net.id64:ff9b::ca98:fef5RFC 6052

Last update: Tue 28 Mar 06:02:02 UTC 2017

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;
        // IPv6 Link local
        fe80::/10;
        // RFC 6052
        64:ff9b::/96;
    } 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.