16/08/12 14:37, intrigeri: > Hi, > > (reference: bugs/ttdnsd_broken) > > commit 30f1fa3a3a56020473a3d5982b84a49475e703fb > Author: Tails developers <[email protected]> > Date: Wed Aug 15 21:50:50 2012 +0200 > > Update the design document to take into account ttdnsd now lives out of > the name resolution loop. > > commit f8e5d97f3c383dae070af4a4e91dd7d8980b30ce > Author: Tails developers <[email protected]> > Date: Wed Aug 15 21:45:17 2012 +0200 > > Remove ttdnsd from the default DNS resolution loop. > > This reverts commits c0dbb73440197d6ee0719f6f0d2ff98a4eabac17 > and 849e922a10411ba7c399bf2e733203f32d6608ab.
At least it works in the sense that `host -t mx boum.org` doesn't report any MX records, as opposed to when that command is run in Tails 0.12.1. It's very glitchy, though, and rarely succeeds when it should. I think this can be attributed to Google's DNS, which currently is configured, which is known to take issue with Tor exits. I have consistently good results with OpenDNS (208.67.222.222), so I recommend a switch if we want this feature to actually be useful. Cheers!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev
