<br><br><div class="gmail_quote">2008/11/10 Matt Riddell <span dir="ltr"><<a href="mailto:lists@venturevoip.com">lists@venturevoip.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="Ih2E3d">On 11/11/2008 1:34 a.m., samuel wrote:<br>
> Folks,<br>
><br>
> I'm tracing this error and looks like newer 1.4 (1.4.22) does not behave as<br>
> I stated (no DNS for channel domainname) and it must have been solved in the<br>
> way from my versions to the newer.<br>
><br>
> I'll update to the newer versions and confirm it.<br>
<br>
</div>Fantastic if that's the case. I've seen quite a few people complaining<br>
about this and actually had an upstream DNS provider change IP :)<br>
<br>
All solved by a caching dns server - achieved in debian by:<br>
<br>
apt-get install bind9<br>
<br>
followed by change nameserver to <a href="http://127.0.0.1" target="_blank">127.0.0.1</a> in resolv.conf</blockquote><div><br>But this does not solve the problem, it's just a global work around.<br><br>Asterisk still makes the queries and if there's some problem in the DNS it will continue blocking the first time the authoritative DNS crashes. The problem is that since the channel is a "random string", the queries can NOT be cached (everytime the domain name is different) and the DNS timeout still occur for every DNS channel query and the asterisk will block at some call rate.<br>
<br>So far I've updated a few machines (1.4.22) and the DNS queries are reduced to a minimum, at least haven't seen DNS channel queries...<br><br>Anyone familiar with this knows whether this issue is solved in 1.6?<br>
<br>Best regards,<br>Samuel.<br><br></div></div><br>