Have been away and not been able to follow up on these suggestions until now. Yes, the good news is that hard coding in the routes in /etc/hosts has solved the problem. I really like the suggestion of doing a regular lookup to check that the IP address has not changed, rather than re-invent the wheel does anyone have a script that might do this?
Terry ---------------------------------------------------------------------- Message: 1 Date: Mon, 18 May 2009 13:38:35 -0400 From: "Terry Stone" <[email protected]> Subject: [Dnsmasq-discuss] Cache Size To: <[email protected]> Message-ID: <00c001c9d7df$79029120$6b07b360$@com> Content-Type: text/plain; charset="us-ascii" I am using DNSMASQ on a server that also runs Trixbox Asterisk IP PBX. Asterisk has an unfortunate trait that if SIP trunks that register with a VOIP provider cannot obtain DNS resolution all SIP extensions stop working for internal phone calls. I installed DNSMASQ in an attempt to stop this from happening, the theory being that DNSMASQ would resolve the address from its cache. This worked fine until I had a long Internet outage when after about 15 minutes things stopped working. My guess is that DNSMASQ flushed the cache and needed to go to another server for updated information. Can anyone tell me how long DNSMASQ holds information in the cache and if it is possible to lengthen that time. Cache size is not an issue as DNSMASQ is only used to resolve the SIP trunk addresses therefore the cache is very small. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/2009051 8/db1c7212/attachment.html ------------------------------ Message: 2 Date: Mon, 18 May 2009 17:07:53 -0400 From: Tom Metro <[email protected]> Subject: Re: [Dnsmasq-discuss] Cache Size To: Terry Stone <[email protected]> Cc: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Terry Stone wrote: > Can anyone tell me how long DNSMASQ holds information in the cache... I would assume the length of time varies per record, as it is something specified as part of the record. It's part of the DNS protocol that the upstream server gets to say how long a record is good for. > ...and if it is possible to lengthen that time. I suspect not. > Asterisk has an unfortunate trait that if SIP trunks that register > with a VOIP provider cannot obtain DNS resolution all SIP extensions > stop working for internal phone calls. Your best bet is probably to make sure this bug is filed with Asterisk and encourage the developers to fix it. Another option might be to use a SIP proxy. That might put a layer between your Asterisk server and your VoIP provider, such that Asterisk doesn't notice when the WAN connection is down. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ ------------------------------ Message: 3 Date: Tue, 19 May 2009 08:39:54 +0200 From: Rune Kock <[email protected]> Subject: Re: [Dnsmasq-discuss] Cache Size To: Terry Stone <[email protected]> Cc: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Mon, May 18, 2009 at 19:38, Terry Stone <[email protected]> wrote: > I am using DNSMASQ on a server that also runs Trixbox Asterisk IP PBX. > Asterisk has an unfortunate trait that if SIP trunks that register with a > VOIP provider cannot obtain DNS resolution all SIP extensions stop working > for internal phone calls. I installed DNSMASQ in an attempt to stop this > from happening, the theory being that DNSMASQ would resolve the address from > its cache. This worked fine until I had a long Internet outage when after > about 15 minutes things stopped working. My guess is that DNSMASQ flushed > the cache and needed to go to another server for updated information. Can > anyone tell me how long DNSMASQ holds information in the cache and if it is > possible to lengthen that time. Cache size is not an issue as DNSMASQ is > only used to resolve the SIP trunk addresses therefore the cache is very > small. Would it be an option for you just to hardcode the response for the most common addresses? (Use a address statements in dnsmasq.conf or use the host file). Rune ------------------------------ Message: 4 Date: Tue, 19 May 2009 06:23:27 -0400 From: RevRagnarok <[email protected]> Subject: Re: [Dnsmasq-discuss] Cache Size To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" > > > Would it be an option for you just to hardcode the response for the > most common addresses? (Use a address statements in dnsmasq.conf or > use the host file). > > That's quite the hack, and I like it. I would expand upon it a little; I would write a small perl script that went into cron.daily or something similar to update the host file in case they ever change, but major vendor IPs won't change all that often... Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/2009051 9/dca9f598/attachment-0001.htm ------------------------------ _______________________________________________ Dnsmasq-discuss mailing list [email protected] http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss End of Dnsmasq-discuss Digest, Vol 48, Issue 8 **********************************************
