bhanupratapys / dnswarden

Adblocking dns, Uncensored dns server and Adult-filter dns. Supports Dns-over-QUIC , Dns-over-HTTPS and Dns-over-TLS with DNSSEC enabled and no logging.
https://dnswarden.com/
MIT License
146 stars 4 forks source link

dnswarden is down in past few hours #16

Closed gloschtla closed 4 years ago

gloschtla commented 4 years ago

in Android 9 "private DNS mode" ...dot.dnswarden.com always worked before. But today it suddenly says "Couldn't connect". Also the customized DNS server in my router's settings made all the devices offline, today.

bhanupratapys commented 4 years ago

Hello, plaintext dns issue should be fixed now. According to my monitoring logs, DoT/DoH was never down. The valid domains for non-ecs DoT are adblock-dot.dnswarden.com , uncensored-dot.dnswarden.com and adult-filter-dot.dnswarden.com.

For ecs support , ecs-adblock-dot.dnswarden.com , ecs-adult-filter-dot.dnswarden.com and ecs-uncensored-dot.dnswarden.com.

If you are located in and around the server region then stick with non-ecs DoT domains.

Also DoT will only work on default port 853 from now on.

Edit : Narrowed down why DoT might have failed for you, all the dns queries for dnswarden domain failed to resolve for couple of hours. My monitoring script uses simple kdig to test the health of DoT servers by directly using ip addresses of the servers, hence it didn't show up in my monitoring logs. Fixed that.

gloschtla commented 4 years ago

I wonder what happened. The router works again, as before: with 116.203.70.156 and the other 3 normal DNS addresses of dnswarden. Only Android still doesnt work in private DNS mode (just now, but now also works again). It always worked before, and nothing was changed in any settings in meantime.

bhanupratapys commented 4 years ago

The router issue which you had is totally my fault, are you still having the problem on android ?

bhanupratapys commented 4 years ago

Closing this, everything is functioning normally after the server upgrade.

In case you find any unusual behaviour, either reopen this issue or a new one.