Getting reports from people in Indonesia that they're unable to access Write.as... Things look fine from where we are, but they're getting this error: DNS_PROBE_FINISHED_NXDOMAIN
Anyone have experience verifying if this is indeed censorship happening, and if so, working around it? Retoots appreciated!
@selea Yep, and we're still seeing some traffic from there. But probably most of our active users are there -- very odd to see so many reports.
Have you considering enablind DNSSEC on the write.as domain btw?
@selea Definitely looks like something we should do. Will probably just need to switch DNS providers, since it doesn't look like our current one supports it
@matt users can try to switch the DNS server they are connecting to, eg. Google DNS (220.127.116.11)
@matt get their DNS server settings and use dig to verify.
Dig @18.104.22.168 domain.com
As an example using Google DNS. If they have poisoned the tree, you'll come up missing or it'll be different results than you think.
You could try adding dnssec to prevent this but that can be hit/miss as well in my experience. Depends on if the down tree consumer respects dnssec properties.
@matt find out what dns servers they're using and also verify that using Google dns 22.214.171.124 and 126.96.36.199 works
@schmittlauch I did try that, but was only able to test from my location... Couldn't figure out how to do it from around the world.
@matt I guess you need to reach out to them.
@matt I'm your man to help.
@matt I tried with a VPN locates in Indonesia but it worked fine for me 🤷♂️
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!