Curious things with MaraDNS
strenholme.usenet at gmail.com
Mon Aug 2 13:50:38 EDT 2010
> $ askmara Asv5.isp4p.net. 184.108.40.206
> # Querying the server with the IP 220.127.116.11
> # Remote server said: TRUNCATED
> # Question: Asv5.isp4p.net.
OK, I have just uploaded a Deadwood snapshot that will work with
packets that need DNS-over-TCP to resolve. It can be downloaded here:
Some things to keep in mind:
* By default, Deadwood disables DNS-over-TCP. Users who need to
handle the very rare hostname that needs DNS-over-TCP to resolve will
need to explicitly enable it by adding the following to their dwood3rc
* Deadwood does not cache packets that need DNS-over-TCP to resolve.
Deadwood only supports DNS-over-TCP for packets stub resolvers can
handle (NS referrals or incomplete CNAME answer packets will not do
the right thing if they need DNS-over-TCP)
* This is only getting fixed for Deadwood, not MaraDNS 1.x
Sebastian: Thank you for the bug report. Let me know of any other
hostnames that Deadwood can not reply, or of any other Deadwood bugs.
Note: I do not answer MaraDNS (including Deadwood) support requests
sent by private email without being compensated for my time. A MaraDNS
support request is any and all discussion you may wish to have about
MaraDNS in private email; if you want to email me to talk about
MaraDNS then, yes, that is a support request. I will discuss rates if
you want this kind of support. Thank you for your understanding.
MaraDNS security vulnerability reports, however, will be dealt with
without charge and kept confidential. If you don't know what Bugtraq
is, then, no, your email is not a security report. It is not a
security report unless you've done due diligence to determine how the
security bug you think you found can reasonably be exploited.
More information about the list