DNS Morons

These people should run Split-horizon DNS;

HostWrong IP addressReason
22.15.78.181.ufinet.com.co64:ff9b::b54e:f16RFC 6052
autoking.com.tr172.16.1.3RFC 1918
ibdxbns4.duhosting.ae10.198.18.14RFC 1918
nhanhoa-rm.nhanhoa.com192.168.102.8RFC 1918
nox.rjf.ca10.0.0.12RFC 1918
ns02.foxinc.com10.215.244.27RFC 1918
ns3.tataidc.co.in64:ff9b::6708:2d05RFC 6052
ns4.abtauto.com10.10.49.148RFC 1918
ns4.tataidc.co.in64:ff9b::6708:2e05RFC 6052
ns5.tataidc.co.in64:ff9b::6708:2c05RFC 6052
resolver1.tigo.com.gt10.90.0.50RFC 1918
s-dns-cvt2-01.pop.ns.selectel.org172.24.87.66RFC 1918

Last update: Sat 17 Apr 06:02:02 UTC 2021

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.