Everything is a Freaking DNS problem

I covered this one before .. but as it struck twiced today .. I think it's worth repeating. Both my collegue Karl and Trent ran into the same problem , within hours hours of eachother, a missing or failing reverse dns mapping that caused performance issues .. and a lot of log entries..

Karl denies having a second life in Perth but I`m not really sure about that ...

But I guess they both have to agree... Everything is a fscking DNS problem.
(I noticed other people using that spelling this weekend, on stage in the Janson)

SANS notes a weird DOS atack on different namesevers. People quering for "." a lot.

Ward wondering what's going on with the .org nameservers

And Dries migrating his site.

Funny how people call clear and obvious DNS problems a
"mail" problem.

Seen over at Failblog, you could call it OS fail also actually .. maybe one day people will realize that AVG correctly identified the Trojan

Tom dropped me a mail today letting me know that all the links to my RSS feed were broken.
I tested, and tested again and failed to reproduce the problem.

The only things I had changed recently where the administrator menu module and Pathauto module, apart from that I had not made any changes. So I tried uninstalling the modules to see if that helped, it didn't. There was no difference between the 2 setups.

When I replied to Tom that I couldn't reproduce the problemm he told me he only had the problem on http://krisbuytaert.be/ and not on http://www.krisbuytaert.be/

So I verified the apache vhost config and it turned out that the problem, as usual, was a frigging DNS problem.
Both Apache vhost config files had a different setup, so depending on how you arrived at this site you got a different config.

Annoying .. but I guess I owe Tom a beer for figuring this out and pointing me to my own DNS problem.

Hits a freaking DNS problem

Darkreading has a report on the next big dns threat according to Paul Mockapetris. DNS corruption. When a user connects to his ISP, or to a Wifi port, certainly a free one.
He has absolutely no idea about the state of the DNS server.

So a user working off a public WiFi port, for example, is at the mercy of the DNS servers it uses, which "could easily be malicious,"

Indeed it might be hacked, it might be modified on purpose, pointing your browser to somesite totally different than you want to .. while you're not expecting it.

Anyway

[sdog@mine ~]$ cat /etc/resolv.conf
nameserver 127.0.0.1

fine DNS problem
Actually not Alfreso but 123-reg