| Private Hosting Questions about VPS, dedicated servers and colocation. |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread |
|
|
#1 (permalink) |
|
Registered User
Seasoned Poster
Joined in Aug 2006
66 posts
Gave thanks: 11
Thanked 0 times
|
How to we test/patch the DNS flaw ?
How can we test and/or patch against this DNS flaw that has been discovered?
|
|
|
|
|
|
#2 (permalink) |
|
Surpass Abuse Admin
Super #1
Joined in Mar 2005
Lives in Houston, TX
Hosted on NONE
7,797 posts
Gave thanks: 11
Thanked 278 times
|
Our DNS resolvers have already been patched against this flaw.
![]()
__________________
Unofficial IRC Channel: #surpass EFNetUnofficial = No official support. Support requests can be submitted to our helpdesk. |
|
|
|
|
|
#4 (permalink) |
|
Surpass Abuse Admin
Super #1
Joined in Mar 2005
Lives in Houston, TX
Hosted on NONE
7,797 posts
Gave thanks: 11
Thanked 278 times
|
This vulnerability applies to DNS resolvers. If your server is using 66.7.207.2 (or anything else on our network) as a resolver, you have nothing to worry about. The server itself is an authoritative name server, rather than a resolver so it is not vulnerable to this type of attack.
__________________
Unofficial IRC Channel: #surpass EFNetUnofficial = No official support. Support requests can be submitted to our helpdesk. |
|
|
|
|
|
#6 (permalink) |
|
Marketing Maven
Surpass Staff
Joined in May 2003
Lives in Orlando
24,748 posts
Gave thanks: 946
Thanked 806 times
|
What I am wondering is the difference between this flaw, and what already existed: Pharming
Pharming - Wikipedia, the free encyclopedia
__________________
|
|
|
|
| This user thanks Kayla for this great post! | Brandonnn (August 10th, 2008) |