Most of the technical community has probably heard of the recently found DNS weakness. The basic premise is that if a recursive nameserver doesn’t use sufficently random source ports when making recursive queries, it can be vulnerable to an attacker who is trying to poisen the cache, or fill it with incorrect data.
I’ve now heard reports about it from various news sources who make it sound much more drastic than it actually is. Granted, it is a serious flaw, but fortunately most companies with any desire for security use SSL, which provides an additional layer for identity verification. Also, for most any company with an IT staff, patching the DNS server with the required fixes should be a fairly trivial task. The most important servers to be fixed are those run by ISPs and Datacenters, both of which should have their servers fixed by now.
Tools for testing your DNS servers are fairly easy to come by. dns-oarc.net has a web-based test, although I don’t know how it discovers your DNS Servers. For windows users, you can run ‘nslookup’ like this:
C:\Documents and Settings\Brandon>nslookup
Default Server: cns.manassaspr.va.dc02.comcast.net
> set type=TXT
porttest.dns-oarc.net canonical name = porttest.y.x.w.v.u.t.s.r.q.p.o.n.m.l.k.
"188.8.131.52 is GREAT: 26 queries in 2.3 seconds from 25 ports with std
To test from a linux machine, you can use dns-oarc’s test with dig like this:
root@server:~# dig porttest.dns-oarc.net in txt +short
"184.108.40.206 is GREAT: 26 queries in 1.2 seconds from 26 ports with std dev 20533"
Your are looking for a response that contains GOOD or GREAT. If your results contain something else, you should notify your ISP or Data Center to have them fix their servers.