Mar 30 2005
Another round of DNS poisoning
This is related to another incident last week, but the new incident involves servers that are not supposed to be vulnerable to the DNS cach poisoning. So, is there a new vector of the poisoning, or is this a different aspect of the same vulnerability? Keep an eye out for traffic bound for 209.123.63.168, 64.21.61.5 and 205.162.201.11.