That's awesome! That's exactly how I was thinking but to be honest I wasn't sure how to implement the background service that ties the query logs to the web server. <br><br>If it wouldn't take too long, do you think you could talk about the specifics a little bit more?
<br><br><div class="gmail_quote">On Dec 30, 2007 5:43 AM, Mike Cardwell <<a href="mailto:tor@lists.grepular.com">tor@lists.grepular.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Mark Manning wrote:<br>> Hello - I'm just starting to pay attention to this mailing list so<br>> forgive me if this subject has been brought up before.<br>><br>> I'm interested in setting up a [or using an existing] service that could
<br>> test for a proper DNS configuration [among other things]. The goal<br>> being that a person could visit a web page to confirm that their DNS<br>> queries were being forwarded through the TOR network and not using a
<br>> local DNS server.<br><br></div><div><div></div><div class="Wj3C7c">I was considering doing something similar but haven't found the time<br>recently. I got around to setting up a basic page which does the DNS<br>
check you're refering to, and also does a check to make sure gopher://<br>requests are being proxied:<br><br><a href="http://clayman.tor.grepular.com/torcheck.cgi" target="_blank">http://clayman.tor.grepular.com/torcheck.cgi
</a><br><br>The DNS check basically works by just turning on binds query logging,<br>and then having a daemon which tails the log file looking for the<br>appropriate requests and then making the data available to the cgi<br>
<br>Regards,<br>Mike<br></div></div></blockquote></div><br>