<div dir="ltr">(You guys confirmed what I was thinking when I started the thread.. <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">thank you all for your replies, they gave me a lot of confidence on DMQ and I'm already testing it out)</span><div><div><div><div><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 30, 2018 at 9:06 AM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Apr 30, 2018 at 11:13:13AM +0200, Aleksandar Sosic wrote:<br>
<br>
> We have a scalable dockerized environment and it's difficult to<br>
> configure DMQ having dynamic IPs, instances booting up and scaling<br>
> down on demand.<br>
<br>
</span>A DNS alias that resolves to multiple entries is a great way to do that:<br>
<br>
<a href="https://kamailio.org/docs/modules/5.1.x/modules/dmq.html#dmq.p.notification_address" rel="noreferrer" target="_blank">https://kamailio.org/docs/<wbr>modules/5.1.x/modules/dmq.<wbr>html#dmq.p.notification_<wbr>address</a><br>
<a href="https://kamailio.org/docs/modules/5.1.x/modules/dmq.html#dmq.p.multi_notify" rel="noreferrer" target="_blank">https://kamailio.org/docs/<wbr>modules/5.1.x/modules/dmq.<wbr>html#dmq.p.multi_notify</a><br>
<br>
although it'd be great if DMQ could exclude the local host from those<br>
notification peers automatically, so that one didn't have to set up<br>
multiple, exclusionary DNS entries for specific instances. Who knows,<br>
maybe it can.<br>
<br>
But in principle, such DNS records can be tied to the internal DNS<br>
resolution of a container discovery mechanism, be it Docker's internal<br>
mechanism or something more like Consul. <br>
<span class="HOEnZb"><font color="#888888"><br>
-- Alex<br>
</font></span><span class="im HOEnZb"><br>
-- <br>
Alex Balashov | Principal | Evariste Systems LLC<br>
<br>
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) <br>
Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
<br>
</span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
</div></div></blockquote></div><br></div>