Lawrence, > > Either your DNS resolver is borked, or your firewall/home-router > > is playing jokes on you. > > Are you using Google Public DNS for this? Don't!
> This is a dedicated server in a facility in the US. The server is > configured to use the resolvers 4.2.2.1 and 4.2.2.2 > > I wouldn't dream of relying on Google for anything :) Like I said, your resolver is tricking you. Either by its own fault, or SpamHaus is intentionally not providing useful results to your DNS resplver: good (my own resolver): $ host -t a midpage.ru.dbl.spamhaus.org. midpage.ru.dbl.spamhaus.org has address 127.0.1.2 good: host -t a midpage.ru.dbl.spamhaus.org resolver1.opendns.com Using domain server: Name: resolver1.opendns.com Address: 208.67.222.222#53 midpage.ru.dbl.spamhaus.org has address 127.0.1.2 bad: $ host -t a midpage.ru.dbl.spamhaus.org. 4.2.2.2 Using domain server: Name: 4.2.2.2 Address: 4.2.2.2#53 bad: $ host -t a midpage.ru.dbl.spamhaus.org. 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 There is no good reason to use ISP's or some public DNS resolver for anything but the smallest home network. Just install 'unbound', or 'bind' in resolving-only mode. Mark
