mesos-dns
mesos-dns copied to clipboard
mesosphere
DNS-based service discovery for Mesos.
So, when Mesos-DNS starts, before it loads the state.json from Mesos, it replies to a result of leader.mesos as follows: ``` 3c075477e55e:mesos-dns sdhillon$ dig -p8053 -t A @127.0.0.1 leader.mesos ;...
Users would like to change the log level without interrupting service. Currently, they have to restart mesos-dns in order to do this. I'd say as far as changing the loglevel...
@spacejam suggested that when Mesos starts up, we poll faster, in order to build up cluster state faster as the entire cluster is coming up.
perhaps should return [404](https://en.wikipedia.org/wiki/HTTP_404) vs something like below? ``` core@ip-10-0-3-57 ~ $ curl -sS master.mesos:8123/v1/services/_chronoz._tcp.marathon.mesos [ { "service": "", "host": "", "ip": "", "port": "" } ] ``` or maybe...
some clients will want to know right away when service records change. it would be ideal if they could watch (ala [k8s](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/devel/api-conventions.md#verbs-on-resources), or [consul](https://www.consul.io/docs/commands/watch.html)) a service for changes. this would...
I'm thinking of how I might bridge kubernetes service discovery and mesos service discovery. Part of a solution might be a mesos-dns "plugin" that watches the kubernetes service registry and...
Dynamic update is a feature that allows additional services to be registered with a central DNS server. Its role in a DNS-based service discovery scheme is summarized well in [IETF...
Replaces #120 [ ] Enable IPv6 socket binding [ ] Generate AAAA records where applicable [ ] Resolve AAAA records where applicable
Right now the "listener" option only takes one IP. It would be good if I could bind mesos-dns to several IPs so that it is available from e.g. the office...
