Hi Jean-Paul,<br><br>I guess my focus is right when it comes to redirecting clients. <br><br>Im hooking into<br><br>DNSDatagramProtocol.writeMessage(self, message, address):<br><br>And I guess thats OK?<br><br>But when it comes to bogus domains, I guess i could use:<br>
<br>DNSServerFactory.gotResolverError(self, failure, protocol, message, address):<br><br>My problem is now how I construct a redirect package and channel it back to the client.<br><br>Do you think that is a sensible approach? -and do you hava a pointer on how to find the associated client.<br>
<br>kind regards<br><br>/tax<br><br><div class="gmail_quote">2009/10/22 <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>></span><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">On 02:46 pm, <a href="mailto:jesper@taxboel.dk">jesper@taxboel.dk</a> wrote:<br>
>Hi Jean-Paul,<br>
><br>
>Thanx for your nice reply. My problem seems to be that I dont get any<br>
>calls<br>
>to writemessage when the domain is a bogus one?<br>
<br>
</div>It's not immediately obvious why this would be. writeMessage is called<br>
to write responses back to your clients. If the requests your server<br>
issues get answers, then writeMessage will be called with those answers.<br>
If it's not being called, perhaps the problem is that your server's<br>
requests are being answered by the servers it is asking.<br>
<div><div></div><div class="h5"><br>
Jean-Paul<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br>