DNS cache poisoning susceptibility

[CPUBUM]

DNS cache poisoning susceptibility, a serious security flaw in DNS recently acknowledged by CERT.

There has been a lot of talk lately about the DNS cache poisoning susceptibility. Can JAG let us know what is being done to make sure all of the dedicated, VPS, and shared servers are protected?

[jason]

Shared servers (GigaDeal, SDX, Reseller) use JPC maintained DNS servers which I remember someone from Jag saying had been patched a long time ago (shortly after the alert came out).

Dedicated and VPS systems are not actively monitored by JPC. Like anything dedicated or VPS, this issue is something that the account owner needs to either patch himself or make a request to JPC to have it patched by them. The good news is that, since many (if not most) of these accounts use some form of control panel, which usually make these patches automatically or with minimal effort of the owner.

There is also little likelihood of these servers (especially the ones on VPS and dedicated boxes in most cases) becoming poisoned because they don't generally cache data from other servers. In the case of my VPS the name servers listed in my resolv.conf are *not* my private nameservers and, since I don't use my private nameservers for anything except resolving my domains, my nameservers cache nothing and are therefore not susceptible.

--Jason

[CPUBUM]

Thanks for the reply Jason. I figured any patched required would be pushed via cPANEL, but you never know... lol