DNS Cache Problems


Warning: Trying to access array offset on value of type bool in /var/www/vhosts/bnshosting.net/httpdocs/wp-content/plugins/wp-social-sharing/includes/class-public.php on line 81

BNSHosting has recently coordinated with several larger ISPs and Telcos in the Philippines to correct some possible DNS spoofing issues. The symptoms are that the targetted website is not being resolved properly by other ISP’s DNS.

This article from US CERT on DNS vulnerability (http://www.kb.cert.org/vuls/id/800113) may shed some light. Some excerpts are reproduced below:

Caching DNS resolvers are primarily at risk–both those that are open (a DNS resolver is open if it provides recursive name resolution for clients outside of its administrative domain), and those that are not. These caching resolvers are the most common target for attackers; however, stub resolvers are also at risk.

An attacker with the ability to conduct a successful cache poisoning attack can cause a nameserver’s clients to contact the incorrect, and possibly malicious, hosts for particular services. Consequently, web traffic, email, and other important network data can be redirected to systems under the attacker’s control

4 thoughts to “DNS Cache Problems”

  1. Hello Chevy,

    No site is free from hackers. They will always attempt to break in. What both of us can do together is make it harder for them to break in.

  2. we plan to use this hosting site for the web portal we’re creating.. is it free from hackers??? what are some security measures i terms of the database? backup?server?

  3. Update:

    At least for one domain, (bnshosting.net), the Name servers were not properly defined by our staff. So this is no way a fault of the PLDT, globe, Bayantel, Digitel DNS servers…

    The humbling lesson here is that we need to do an audit of DNS settings on a periodic basis to make sure that settings are updated.

    Our thanks to our friends in the telcos that worked with us to isolate the issues.

  4. I already noticed this since last month. Our domain name which was resolved to our coloc server for a long time already suddenly got resolved to another ip address or worst was resolved to nothing at all.

Leave a Reply