These people should run Split-horizon DNS;
| Host | Wrong IP address | Reason |
|---|---|---|
| ibauhns3.duhosting.ae | 10.79.128.18 | RFC 1918 |
| ns1.banksys.be | 172.16.23.71 | RFC 1918 |
| ns1.comeconnect.com | 64:ff9b::caa4:2051 | RFC 6052 |
| ns2.comeconnect.com | 64:ff9b::caa4:2052 | RFC 6052 |
| ns3.tataidc.co.in | 64:ff9b::6708:2d05 | RFC 6052 |
| ns4.tataidc.co.in | 64:ff9b::6708:2e05 | RFC 6052 |
| ns5.tataidc.co.in | 64:ff9b::6708:2c05 | RFC 6052 |
Last update: Tue 27 Jun 06:02:01 UTC 2017
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.