For example, the solitaire card game. Bu it appears to happen with all<br>applications. I don't believe it is coming from the application but<br>somewhere in the system code that launches the app.<br><br>I used wireshark. let wireshark run. no traffic. Launch an app.<br>
As soon as it is up, check wireshark. There are several packets shone,<br>including the DNS queries. Also, it appears no use is made of the<br>DNS queries in that I do not see follow up traffic.<br><br>Since it is not a particular application I don't know how I would use<br>
strace.<br><br>I did forget to mention one important difference between my laptop<br>and desktop. The laptop is running gnome while my desktop is<br>running KDE. When I thought about this I began to think maybe<br>gnome is responsible but I don't know how to check this.<br>
<br>Richard<br><br><div class="gmail_quote">On Wed, Oct 28, 2009 at 1:24 AM, Rick Moen <span dir="ltr"><<a href="mailto:rick@linuxmafia.com">rick@linuxmafia.com</a>></span> 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="im">Quoting Richard Harke (<a href="mailto:paleopenguin@gmail.com">paleopenguin@gmail.com</a>):<br>
<br>
</div><div class="im">> That leaves the question: why access DNS at all for a application launch?<br>
<br>
</div>Again, what application, for example? And by what means do you know<br>
that that application is doing DNS lookups? You say "I've done some<br>
tracing", but I don't know what you've done to associate DNS lookups<br>
with particular non-network-oriented applicaitons.<br>
<br>
Once you know what application binary you're talking about, you can run<br>
it under strace to determine what system calls it's making.<br>
<br>
By the way, IMO, you really should consider running and using a local<br>
recursive DNS nameserver. Doing so improve performance a great deal<br>
over using your "router on your home network", which almost certainly is<br>
merely a forwarder. It'll also improve performance over using OpenDNS,<br>
along with not giving the operators of that service detailed<br>
information about your Internet activity, _and_ (unlike OpenDNS) it<br>
would actually implement DNS technical standards correctly (i.e.,<br>
correctly answering "NXDOMAIN" when that's the truth).<br>
<br>
Possibly of related interest:<br>
<a href="http://linuxmafia.com/pipermail/sf-lug/2008q3/005308.html" target="_blank">http://linuxmafia.com/pipermail/sf-lug/2008q3/005308.html</a><br>
<a href="http://linuxmafia.com/pipermail/sf-lug/2008q3/005309.html" target="_blank">http://linuxmafia.com/pipermail/sf-lug/2008q3/005309.html</a><br>
<div><div></div><div class="h5">_______________________________________________<br>
vox-tech mailing list<br>
<a href="mailto:vox-tech@lists.lugod.org">vox-tech@lists.lugod.org</a><br>
<a href="http://lists.lugod.org/mailman/listinfo/vox-tech" target="_blank">http://lists.lugod.org/mailman/listinfo/vox-tech</a><br>
</div></div></blockquote></div><br>