Re: fyi: mesos-dns is not registering all ip addresses
+Jason Kölker
On Mon, Jul 27, 2020 at 8:03 AM Alex Evonosky
wrote:
> Thank you Marc for the clarification.
>
>
>
> On Mon, Jul 27, 2020 at 8:50 AM Marc Roos
> wrote:
>
>>
>> Hi Alex,
>>
>> My config.json is quite similar, but having "IPSources": ["netinfo",
>> "mesos", "host"]
>>
>> You will only run into this issue when you have multihomed tasks, having
>> two or more network adapters, eth0, eth1 etc
>>
>>
>>
>>
>> -Original Message-
>> From: Alex Evonosky [mailto:alex.evono...@gmail.com]
>> Sent: maandag 27 juli 2020 14:36
>> To: user@mesos.apache.org
>> Subject: Re: fyi: mesos-dns is not registering all ip addresses
>>
>> thank you.
>>
>> We have been running mesos-dns for years now without any issues. The
>> docker apps spin up on marathon and automatically gets picked up by
>> mesos-dns...
>>
>> This is our config.json:
>>
>>
>> {
>> "zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
>> "masters": ["10.10.10.51:5050", "10.10.10.52:5050",
>> "10.10.10.53:5050"],
>> "refreshSeconds": 3,
>> "ttl": 3,
>> "domain": "mesos",
>> "port": 53,
>> "resolvers": ["10.10.10.88", "10.10.10.86"],
>> "timeout": 3,
>> "httpon": true,
>> "dnson": true,
>> "httpport": 8123,
>> "externalon": true,
>> "listener": "0.0.0.0",
>> "SOAMname": "ns1.mesos",
>> "SOARname": "root.ns1.mesos",
>> "SOARefresh": 5,
>> "SOARetry": 600,
>> "SOAExpire": 86400,
>> "SOAMinttl": 5,
>> "IPSources":["mesos", "host"]
>> }
>>
>>
>>
>>
>> we just have our main DNS resolvers have a zone "mesos.marathon" and
>> forwards the request to this cluster...
>>
>>
>>
>> On Mon, Jul 27, 2020 at 3:56 AM Marc Roos
>> wrote:
>>
>>
>>
>>
>> I am not sure if mesos-dns is discontinued. But for the ones
>> still
>> using
>> it, in some cases it does not register all tasks ip addresses.
>>
>> The default[2] works, but if you have this setup[1] it will only
>> register one ip address 192.168.122.140 and not the 2nd. I filed
>> issue a
>> year ago or so[3]
>>
>>
>>
>> [3]
>> https://github.com/mesosphere/mesos-dns/issues/54145
>> https://issues.apache.org/jira/browse/MESOS-10164
>>
>> [1]
>> "network_infos": [
>> {
>> "ip_addresses": [
>> {
>> "protocol": "IPv4",
>> "ip_address": "192.168.122.140"
>> }
>> ]
>> },
>> {
>> "ip_addresses": [
>> {
>> "protocol": "IPv4",
>> "ip_address": "192.168.10.17"
>> }
>> ],
>> }
>> ]
>>
>>
>> [2]
>> "network_infos": [
>> {
>> "ip_addresses": [
>> {
>> "protocol": "IPv4",
>> "ip_address": "12.0.1.2"
>> },
>> {
>> "protocol": "IPv6",
>> "ip_address": "fd01:b::1:8000:2"
>> }
>> ],
>> }
>> ]
>>
>>
>>
>>
>>
>>
Re: fyi: mesos-dns is not registering all ip addresses
Thank you Marc for the clarification.
On Mon, Jul 27, 2020 at 8:50 AM Marc Roos wrote:
>
> Hi Alex,
>
> My config.json is quite similar, but having "IPSources": ["netinfo",
> "mesos", "host"]
>
> You will only run into this issue when you have multihomed tasks, having
> two or more network adapters, eth0, eth1 etc
>
>
>
>
> -Original Message-
> From: Alex Evonosky [mailto:alex.evono...@gmail.com]
> Sent: maandag 27 juli 2020 14:36
> To: user@mesos.apache.org
> Subject: Re: fyi: mesos-dns is not registering all ip addresses
>
> thank you.
>
> We have been running mesos-dns for years now without any issues. The
> docker apps spin up on marathon and automatically gets picked up by
> mesos-dns...
>
> This is our config.json:
>
>
> {
> "zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
> "masters": ["10.10.10.51:5050", "10.10.10.52:5050",
> "10.10.10.53:5050"],
> "refreshSeconds": 3,
> "ttl": 3,
> "domain": "mesos",
> "port": 53,
> "resolvers": ["10.10.10.88", "10.10.10.86"],
> "timeout": 3,
> "httpon": true,
> "dnson": true,
> "httpport": 8123,
> "externalon": true,
> "listener": "0.0.0.0",
> "SOAMname": "ns1.mesos",
> "SOARname": "root.ns1.mesos",
> "SOARefresh": 5,
> "SOARetry": 600,
> "SOAExpire": 86400,
> "SOAMinttl": 5,
> "IPSources":["mesos", "host"]
> }
>
>
>
>
> we just have our main DNS resolvers have a zone "mesos.marathon" and
> forwards the request to this cluster...
>
>
>
> On Mon, Jul 27, 2020 at 3:56 AM Marc Roos
> wrote:
>
>
>
>
> I am not sure if mesos-dns is discontinued. But for the ones still
> using
> it, in some cases it does not register all tasks ip addresses.
>
> The default[2] works, but if you have this setup[1] it will only
> register one ip address 192.168.122.140 and not the 2nd. I filed
> issue a
> year ago or so[3]
>
>
>
> [3]
> https://github.com/mesosphere/mesos-dns/issues/54145
> https://issues.apache.org/jira/browse/MESOS-10164
>
> [1]
> "network_infos": [
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "192.168.122.140"
> }
> ]
> },
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "192.168.10.17"
> }
> ],
> }
> ]
>
>
> [2]
> "network_infos": [
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "12.0.1.2"
> },
> {
> "protocol": "IPv6",
> "ip_address": "fd01:b::1:8000:2"
> }
> ],
> }
> ]
>
>
>
>
>
>
RE: fyi: mesos-dns is not registering all ip addresses
Hi Alex,
My config.json is quite similar, but having "IPSources": ["netinfo",
"mesos", "host"]
You will only run into this issue when you have multihomed tasks, having
two or more network adapters, eth0, eth1 etc
-Original Message-
From: Alex Evonosky [mailto:alex.evono...@gmail.com]
Sent: maandag 27 juli 2020 14:36
To: user@mesos.apache.org
Subject: Re: fyi: mesos-dns is not registering all ip addresses
thank you.
We have been running mesos-dns for years now without any issues. The
docker apps spin up on marathon and automatically gets picked up by
mesos-dns...
This is our config.json:
{
"zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
"masters": ["10.10.10.51:5050", "10.10.10.52:5050",
"10.10.10.53:5050"],
"refreshSeconds": 3,
"ttl": 3,
"domain": "mesos",
"port": 53,
"resolvers": ["10.10.10.88", "10.10.10.86"],
"timeout": 3,
"httpon": true,
"dnson": true,
"httpport": 8123,
"externalon": true,
"listener": "0.0.0.0",
"SOAMname": "ns1.mesos",
"SOARname": "root.ns1.mesos",
"SOARefresh": 5,
"SOARetry": 600,
"SOAExpire": 86400,
"SOAMinttl": 5,
"IPSources":["mesos", "host"]
}
we just have our main DNS resolvers have a zone "mesos.marathon" and
forwards the request to this cluster...
On Mon, Jul 27, 2020 at 3:56 AM Marc Roos
wrote:
I am not sure if mesos-dns is discontinued. But for the ones still
using
it, in some cases it does not register all tasks ip addresses.
The default[2] works, but if you have this setup[1] it will only
register one ip address 192.168.122.140 and not the 2nd. I filed
issue a
year ago or so[3]
[3]
https://github.com/mesosphere/mesos-dns/issues/54145
https://issues.apache.org/jira/browse/MESOS-10164
[1]
"network_infos": [
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "192.168.122.140"
}
]
},
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "192.168.10.17"
}
],
}
]
[2]
"network_infos": [
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "12.0.1.2"
},
{
"protocol": "IPv6",
"ip_address": "fd01:b::1:8000:2"
}
],
}
]
Re: fyi: mesos-dns is not registering all ip addresses
thank you.
We have been running mesos-dns for years now without any issues. The
docker apps spin up on marathon and automatically gets picked up by
mesos-dns...
This is our config.json:
{
"zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
"masters": ["10.10.10.51:5050", "10.10.10.52:5050", "10.10.10.53:5050"],
"refreshSeconds": 3,
"ttl": 3,
"domain": "mesos",
"port": 53,
"resolvers": ["10.10.10.88", "10.10.10.86"],
"timeout": 3,
"httpon": true,
"dnson": true,
"httpport": 8123,
"externalon": true,
"listener": "0.0.0.0",
"SOAMname": "ns1.mesos",
"SOARname": "root.ns1.mesos",
"SOARefresh": 5,
"SOARetry": 600,
"SOAExpire": 86400,
"SOAMinttl": 5,
"IPSources":["mesos", "host"]
}
we just have our main DNS resolvers have a zone "mesos.marathon" and
forwards the request to this cluster...
On Mon, Jul 27, 2020 at 3:56 AM Marc Roos wrote:
>
>
> I am not sure if mesos-dns is discontinued. But for the ones still using
> it, in some cases it does not register all tasks ip addresses.
>
> The default[2] works, but if you have this setup[1] it will only
> register one ip address 192.168.122.140 and not the 2nd. I filed issue a
> year ago or so[3]
>
>
>
> [3]
> https://github.com/mesosphere/mesos-dns/issues/54145
> https://issues.apache.org/jira/browse/MESOS-10164
>
> [1]
> "network_infos": [
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "192.168.122.140"
> }
> ]
> },
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "192.168.10.17"
> }
> ],
> }
> ]
>
>
> [2]
> "network_infos": [
> {
> "ip_addresses": [
> {
> "protocol": "IPv4",
> "ip_address": "12.0.1.2"
> },
> {
> "protocol": "IPv6",
> "ip_address": "fd01:b::1:8000:2"
> }
> ],
> }
> ]
>
>
>
fyi: mesos-dns is not registering all ip addresses
I am not sure if mesos-dns is discontinued. But for the ones still using
it, in some cases it does not register all tasks ip addresses.
The default[2] works, but if you have this setup[1] it will only
register one ip address 192.168.122.140 and not the 2nd. I filed issue a
year ago or so[3]
[3]
https://github.com/mesosphere/mesos-dns/issues/54145
https://issues.apache.org/jira/browse/MESOS-10164
[1]
"network_infos": [
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "192.168.122.140"
}
]
},
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "192.168.10.17"
}
],
}
]
[2]
"network_infos": [
{
"ip_addresses": [
{
"protocol": "IPv4",
"ip_address": "12.0.1.2"
},
{
"protocol": "IPv6",
"ip_address": "fd01:b::1:8000:2"
}
],
}
]
