22 Sep
2016
22 Sep
'16
9:19 a.m.
Hi,
On 22 September 2016 at 14:08, José Seabra <joseseabra4(a)gmail.com> wrote:
Hi charles,
Inline
Thanks
2016-09-22 13:51 GMT+01:00 Charles Chance <charles.chance(a)sipcentric.com>om>:
Understood, thanks - I misread the following...
Hi José,
In your config, you need to tell DMQ about a minimum of one other node.
This can be in the form of an IP or FQDN - however, where the FQDN resolves
to a single IP, it does not make sense to perform anything other than an A
lookup, so you should set the parameter to 0 in this case.
The number of nodes in your cluster is irrelevant - once started, DMQ
will contact the one you have told it about and learn about the others
automatically.
Optionally, you can tell DMQ about multiple nodes upfront (to account for
instances where the first one may be down or unreachable), by giving it an
FQDN which resolves to multiple IP addresses - in which case you'll need to
set the multi_notify parameter to 1.
> This
is the reason that I'm using multi_notify, the doubt here was why
it is
querying dns using SRV without service specification.
>>>> Another doubt is when we use a FQDN
that only resolves as A record,
>>>> would be better DMQ send only a A query or is there any reason for
always
>>>> try SRV?
>>>>
>>>>
...to mean a scenario in which the FQDN resolves to a single IP
only. My
mistake!
I'll take a look into adding service specification later today.
Cheers,
Charles
--
Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered
office: Faraday Wharf, Innovation Birmingham Campus, Holt Street,
Birmingham Science Park, Birmingham B7 4BB.