<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-CARRIBEAN link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>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?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Terry<o:p></o:p></p>
<p class=MsoPlainText>----------------------------------------------------------------------<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Message: 1<o:p></o:p></p>
<p class=MsoPlainText>Date: Mon, 18 May 2009 13:38:35 -0400<o:p></o:p></p>
<p class=MsoPlainText>From: "Terry Stone" <terry@beach-works.com><o:p></o:p></p>
<p class=MsoPlainText>Subject: [Dnsmasq-discuss] Cache Size<o:p></o:p></p>
<p class=MsoPlainText>To: <dnsmasq-discuss@lists.thekelleys.org.uk><o:p></o:p></p>
<p class=MsoPlainText>Message-ID: <00c001c9d7df$79029120$6b07b360$@com><o:p></o:p></p>
<p class=MsoPlainText>Content-Type: text/plain; charset="us-ascii"<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I am using DNSMASQ on a server that also runs Trixbox
Asterisk IP PBX.<o:p></o:p></p>
<p class=MsoPlainText>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.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-------------- next part --------------<o:p></o:p></p>
<p class=MsoPlainText>An HTML attachment was scrubbed...<o:p></o:p></p>
<p class=MsoPlainText>URL: <a
href="http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090518/db1c7212/attachment.html">http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090518/db1c7212/attachment.html</a>
<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>------------------------------<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Message: 2<o:p></o:p></p>
<p class=MsoPlainText>Date: Mon, 18 May 2009 17:07:53 -0400<o:p></o:p></p>
<p class=MsoPlainText>From: Tom Metro <tmetro+dnsmasq@gmail.com><o:p></o:p></p>
<p class=MsoPlainText>Subject: Re: [Dnsmasq-discuss] Cache Size<o:p></o:p></p>
<p class=MsoPlainText>To: Terry Stone <terry@beach-works.com><o:p></o:p></p>
<p class=MsoPlainText>Cc: dnsmasq-discuss@lists.thekelleys.org.uk<o:p></o:p></p>
<p class=MsoPlainText>Message-ID: <4A11CE29.3090508@gmail.com><o:p></o:p></p>
<p class=MsoPlainText>Content-Type: text/plain; charset=ISO-8859-1;
format=flowed<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Terry Stone wrote:<o:p></o:p></p>
<p class=MsoPlainText>> Can anyone tell me how long DNSMASQ holds
information in the cache...<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>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.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> ...and if it is possible to lengthen that time.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I suspect not.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> Asterisk has an unfortunate trait that if SIP trunks
that register <o:p></o:p></p>
<p class=MsoPlainText>> with a VOIP provider cannot obtain DNS resolution
all SIP extensions <o:p></o:p></p>
<p class=MsoPlainText>> stop working for internal phone calls.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Your best bet is probably to make sure this bug is filed
with Asterisk and encourage the developers to fix it.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>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.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> -Tom<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>--<o:p></o:p></p>
<p class=MsoPlainText>Tom Metro<o:p></o:p></p>
<p class=MsoPlainText>Venture Logic, Newton, MA, USA<o:p></o:p></p>
<p class=MsoPlainText>"Enterprise solutions through open source."<o:p></o:p></p>
<p class=MsoPlainText>Professional Profile: <a
href="http://tmetro.venturelogic.com/">http://tmetro.venturelogic.com/</a><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>------------------------------<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Message: 3<o:p></o:p></p>
<p class=MsoPlainText>Date: Tue, 19 May 2009 08:39:54 +0200<o:p></o:p></p>
<p class=MsoPlainText>From: Rune Kock <rune.kock@gmail.com><o:p></o:p></p>
<p class=MsoPlainText>Subject: Re: [Dnsmasq-discuss] Cache Size<o:p></o:p></p>
<p class=MsoPlainText>To: Terry Stone <terry@beach-works.com><o:p></o:p></p>
<p class=MsoPlainText>Cc: dnsmasq-discuss@lists.thekelleys.org.uk<o:p></o:p></p>
<p class=MsoPlainText>Message-ID:<o:p></o:p></p>
<p class=MsoPlainText> <fa8654f10905182339n73acbbc7u90738b3ae07493df@mail.gmail.com><o:p></o:p></p>
<p class=MsoPlainText>Content-Type: text/plain; charset=ISO-8859-1<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>On Mon, May 18, 2009 at 19:38, Terry Stone <<a
href="mailto:terry@beach-works.com">terry@beach-works.com</a>> wrote:<o:p></o:p></p>
<p class=MsoPlainText>> I am using DNSMASQ on a server that also runs
Trixbox Asterisk IP PBX.<o:p></o:p></p>
<p class=MsoPlainText>> Asterisk has an unfortunate trait that if SIP trunks
that register with a<o:p></o:p></p>
<p class=MsoPlainText>> VOIP provider cannot obtain DNS resolution all SIP
extensions stop working<o:p></o:p></p>
<p class=MsoPlainText>> for internal phone calls. I installed DNSMASQ in an
attempt to stop this<o:p></o:p></p>
<p class=MsoPlainText>> from happening, the theory being that DNSMASQ would
resolve the address from<o:p></o:p></p>
<p class=MsoPlainText>> its cache. This worked fine until I had a long
Internet outage when after<o:p></o:p></p>
<p class=MsoPlainText>> about 15 minutes things stopped working. My guess is
that DNSMASQ flushed<o:p></o:p></p>
<p class=MsoPlainText>> the cache and needed to go to another server for
updated information. Can<o:p></o:p></p>
<p class=MsoPlainText>> anyone tell me how long DNSMASQ holds information in
the cache and if it is<o:p></o:p></p>
<p class=MsoPlainText>> possible to lengthen that time. Cache size is not an
issue as DNSMASQ is<o:p></o:p></p>
<p class=MsoPlainText>> only used to resolve the SIP trunk addresses
therefore the cache is very<o:p></o:p></p>
<p class=MsoPlainText>> small.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Would it be an option for you just to hardcode the
response for the<o:p></o:p></p>
<p class=MsoPlainText>most common addresses? (Use a address statements in
dnsmasq.conf or<o:p></o:p></p>
<p class=MsoPlainText>use the host file).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Rune<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>------------------------------<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Message: 4<o:p></o:p></p>
<p class=MsoPlainText>Date: Tue, 19 May 2009 06:23:27 -0400<o:p></o:p></p>
<p class=MsoPlainText>From: RevRagnarok <DNSMasq@RevRagnarok.com><o:p></o:p></p>
<p class=MsoPlainText>Subject: Re: [Dnsmasq-discuss] Cache Size<o:p></o:p></p>
<p class=MsoPlainText>To: dnsmasq-discuss@lists.thekelleys.org.uk<o:p></o:p></p>
<p class=MsoPlainText>Message-ID:<o:p></o:p></p>
<p class=MsoPlainText> <adbca2d50905190323h420436b1qbd13b2d8e5b6829c@mail.gmail.com><o:p></o:p></p>
<p class=MsoPlainText>Content-Type: text/plain; charset="iso-8859-1"<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Would it be an option for you just to hardcode the
response for the<o:p></o:p></p>
<p class=MsoPlainText>> most common addresses? (Use a address
statements in dnsmasq.conf or<o:p></o:p></p>
<p class=MsoPlainText>> use the host file).<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>That's quite the hack, and I like it. I would expand upon
it a little; I<o:p></o:p></p>
<p class=MsoPlainText>would write a small perl script that went into cron.daily
or something<o:p></o:p></p>
<p class=MsoPlainText>similar to update the host file in case they ever change,
but major vendor<o:p></o:p></p>
<p class=MsoPlainText>IPs won't change all that often...<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> Aaron<o:p></o:p></p>
<p class=MsoPlainText>-------------- next part --------------<o:p></o:p></p>
<p class=MsoPlainText>An HTML attachment was scrubbed...<o:p></o:p></p>
<p class=MsoPlainText>URL: <a
href="http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090519/dca9f598/attachment-0001.htm">http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090519/dca9f598/attachment-0001.htm</a>
<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>------------------------------<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>_______________________________________________<o:p></o:p></p>
<p class=MsoPlainText>Dnsmasq-discuss mailing list<o:p></o:p></p>
<p class=MsoPlainText><a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><o:p></o:p></p>
<p class=MsoPlainText><a
href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>End of Dnsmasq-discuss Digest, Vol 48, Issue 8<o:p></o:p></p>
<p class=MsoPlainText>**********************************************<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>