If I understand the problem, it's that the IP address changes, perhaps is dynamically allocated.
Pablo, ZeroMQ works just as if you were using TCP here; the connection remains open unless the peer disappears. If you want to force a socket to re-connect you need to close it and reopen it. You might think about using ZeroMQ itself to signal address changes, perhaps even to propagate endpoint information. On Mon, Oct 21, 2013 at 7:58 PM, Charles Remes <[email protected]> wrote: > There is no flag or configuration option to work around that. > > I would recommend handling name resolution directly in your code and then > building the transport connection string using the resulting IP address. > > Make sense? > > cr > > On Oct 21, 2013, at 11:03 AM, pablo fernandez <[email protected]> > wrote: > > We're serving a zmq_proxy through DNS and would like clients to "re-resolve" > the DNS address after some period of time. AFAIK sockets now cache the dns > value forever, this is inconvenient. > > Is there a config flag or workaround that doesn't involve > disconnecting/connecting all clients after a period of time? > > Thank you. > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > -- - Pieter Hintjens CEO of iMatix.com Founder of ZeroMQ community blog: http://hintjens.com _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
