These people should run Split-horizon DNS;
| Host | Wrong IP address | Reason |
|---|---|---|
| ins0.shu.ac.uk | 10.14.72.125 | RFC 1918 |
| none.underplatform.com | 192.168.6.177 | RFC 1918 |
| ns3.nbtc.go.th | 172.19.1.4 | RFC 1918 |
| ns4.nbtc.go.th | 172.19.1.5 | RFC 1918 |
| recursor01.haj.ipfire.org | 172.28.1.182 | RFC 1918 |
| recursor02.haj.ipfire.org | 172.28.1.193 | RFC 1918 |
| resolver3.severen.net | fe80::250:56ff:fe9c:36b5 | IPv6 Link local |
| spk.laws.ms | 10.0.5.1 | RFC 1918 |
| worker1.axfr.transip.nl | 10.100.4.15 | RFC 1918 |
| www.dreambox-blog.com | fe80::882c:dfff:fe03:de02 | IPv6 Link local |
Last update: Fri 25 Sep 06:02:01 UTC 2026
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.