Hi!
(open)ser also has similar problems to due lack of asynch
DNS - but at
least they allow to configure DNS timeouts. Thus, a
workaround is
setting low timeout values. I do not know if Asterisk
supports this -
but surely will be easier to implement than asynch DNS.
regards
klaus
Kristian Kielhofner wrote:
> On 6/20/07, Jeffrey C. Ollie <jeff ocjtech.us> wrote:
>> On Wed, 2007-06-20 at 15:13 -0400, Kristian
Kielhofner wrote:
>>> It appears that a good start would be making
Asterisk DNS resolution
>>> asynchronous inside of dns.c and making dns
manager work with
>>> chan_sip. Or maybe not. Does anyone with more
clue have any better
>>> ideas?
>> Outside of making every DNS lookup in Asterisk
asynchronous, your best
>> bet would be to run BIND as a caching-only
nameserver on the Asterisk
>> box. Change the resolv.conf to point to 127.0.0.1.
If you need to run
>> DNS queries through your ISP's nameservers you can
tell BIND to forward
>> all queries through those nameservers.
>>
>> Jeff
>>
>
> Jeff,
>
> I have used that "solution" with mixed
results in the past (usually
> using dnsmasq). The problem is that no good DNS Cache
will cache a
> result longer than the TTL on the record so your
"success" using this
> solution will depend more on the TTL than anything
else...
>
> I'd like to fix the real problem in Asterisk and not
depend on any
> external hacks. This includes:
>
> - DNS Caches
> - Hosts files
> - etc
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|