You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
i build consul in docker ,and run it on marathon, i'm a little confused ,should consul expose some port like mesos-dns , and should i change the /etc/resolve.conf ,point the nameserver to consul's IP ,
and i see consul-temples the command like this
Yes, port 8500 belongs to Consul's REST API. It also optionally exposes a DNS listener in port 8600. You can use that to do things like DNS SRV requests to get host/port info for deployed services.
If you want to use Consul DNS, then you should deploy dnsmasq, point /etc/resolv.conf to the dnsmasq ip / port, and then set up dnsmasq to use consul's port 8600 to route all service.consul. domains to that DNS server, leaving all of the other DNS requests alone.
i build consul in docker ,and run it on marathon, i'm a little confused ,should consul expose some port like mesos-dns , and should i change the /etc/resolve.conf ,point the nameserver to consul's IP ,
and i see consul-temples the command like this
$ consul-template
-consul 127.0.0.1:8500
-template "/tmp/template.ctmpl:/var/www/nginx.conf:service nginx restart"
-retry 30s
-once
is the port 8500 belong to consul ?
The text was updated successfully, but these errors were encountered: