22 Dec

DNS hack of Google, Facebook & more sites in .bd

Yesterday Google’s Bangladeshi website google.com.bd was hacked and this happened via DNS. It was reported on the bdNOG mailing list at morning in a thread started by Mr Omar Ali where he shared this screenshot:

 

 

This clearly shows how authoritative DNS for “com.bd.” (which is same as bd. btw) was poisoned and was reflecting attackers authoritative DNS. Later Mr Farhad Ahmed posted a screenshot of google.com.bd showing hackers page:

 

 

Later Mr Sumon Ahmed mentioned that it happened because web frontend of .bd was compromised. This was an interesting hijack as attacker attacked the key infrastructure of the registry instead of Google or Facebook servers. It’s also a warm reminder of the way DNS depends on the hierarchal structure by design and at this stage, we need to focus on DNSSEC to add on the security to the current system.

 

Lately .bd domain faced issues multiple time this year. I hope it will have a good stable time in the upcoming year. In terms of stability it is being backed by PCH’s anycast infrastructure but PCH’s DNS servers are just published in NS records of it’s existing auth servers, but not on the parent zone (which is root zone). Thus the point of failure remains and is yet to be fixed.

 

 

05 Oct

Partial outage on .bd ccTLD on 5th Oct 2016

outage

 

Bangladesh’s .bd ccTLD faced another outage. As I mentioned in one of the previous posts – .bd domain seems to be primarily on BTCL (AS17494). Zone delegation of .bd is still pending with PCH and while PCH is mentioned in NS records of the authoritative DNS servers but delegation is pending in the root DNS servers as per reply from Kabindra from PCH on the bdNOG mailing list during the last outage.

If we look at root DNS zone .bd has following delegations:

 

After last outage few people started tracking uptime using RIPE Atlas Probes. Thus this time, we do know about the downtime.

Following RIPE Atlas measurements were tracking the DNS checks on jamuna.btcl.net.bd.
4598529 and 4598527. As per measurement ID 4598529, it wasn’t available from 15:44UTC on 4th Oct till 05:44UTC on 5th Oct 2016. This outage was visible from RIPE Atlas probes hosted in India, Singapore, Hong Kong, Japan and Germany.

jamuna.btcl.net.bd. measurement

 

At this point, it’s not known for the cause of the issue. It was mentioned on the bdNOG mailing list today.