> > (1) How are the A records used? Don't you also need to know the port to > talk to the service? >
Whenever you use a hostname (e.g., if you type "ping www.google.com") you use an A record for IPv4 or an AAAA record for IPv6. A records say nothing about port numbers, you have to take care of this yourself somehow (e.g., using the default port). > (2) For SRV records, do applications need to be updated to use DNS > libraries > <http://linux.die.net/man/3/res_init> directly? It looks like > getaddrinfo() > doesn't deal with SRV records. > Getddrinfo() definitely uses on A or AAAA records. res_init() should allow you to query everything your nameserver supports, including SRV records. There are some caveat though: if someone has entered entries in /etc/resolv.conf then you will miss them with res_init() (see http://stackoverflow.com/questions/17419123/getaddrinfo-vs-naptr-srv-record ). > (3) Is there any way to reach the services via a browser using this? It > looks like browsers don't support SRV? > No browser is currently supporting SRV records despite the repeated requests: https://bugzilla.mozilla.org/show_bug.cgi?id=14328 https://code.google.com/p/chromium/issues/detail?id=22423 ... For Mesos systems, here is what I suggest we do: we using something like OVS or one of the many alternative vswitches or vrouters or bridges to assign an IP per task or an IP per executor. Then use default ports. Mesos-DNS will point you to the right IP address through A or AAAA records. > > On Sun, Jan 25, 2015 at 8:57 AM, Christos Kozyrakis < > [email protected]> > wrote: > > > Hi Tom, > > > > the protobuf changes for service discovery will hopefully make it to the > > 0.22 release and we will update the A and SRV record generator to take > > advantage of them. > > > > We still have to decide what naming schemes to support based on this > > information. I suspect that we will have to support a few alternatives. > For > > example some prefer something simple (e.g. search.mesos), while others > some > > more complex (search.prod.europe.mesos). If you have preferences, please > > add them at https://github.com/mesosphere/mesos-dns/issues > > > > Thanks > > > > On Sun, Jan 25, 2015 at 3:19 AM, Tom Arnfeld <[email protected]> wrote: > > > > > Thanks for sharing! Does this project by any chance utilise the new > (not > > > sure if merged or released) service discovery protobufs in Mesos? > > > > > > -- > > > > > > > > > Tom Arnfeld > > > > > > Developer // DueDil > > > > > > > > > > > > > > > > > > (+44) 7525940046 > > > > > > 25 Christopher Street, London, EC2A 2BS > > > > > > On Sat, Jan 24, 2015 at 5:20 PM, Christos Kozyrakis > > > <[email protected]> wrote: > > > > > > > A few days ago, we open sourced a simple DNS server for Mesos > clusters > > > that > > > > automatically draws information from the Mesos master(s). It should > be > > > > helpful for service discovery in multi-framework clusters. > > > > The code: https://github.com/mesosphere/mesos-dns > > > > Docs: https://mesosphere.github.com/mesos-dns > > > > Looking forward your feedback > > > > The Mesosphere team > > > > http://www.mesosphere.com > > > > > >
