mesos-dns: Host not found (NXDOMAIN) with host command

Hello,

I’ve setup mesos-dns and when I use the host command I’m able to resolve a host. If I run the same command right after it. I get a Host not found. I have to wait 60sec (TTL time in config.json) before I can run it again successfully. Running the dig command works all the time.

Any thoughts about this problem ?

# host leader.mesos
leader.mesos has address 10.20.6.123
Host leader.mesos not found: 3(NXDOMAIN)
# host leader.mesos
Host leader.mesos not found: 3(NXDOMAIN)

Thanks

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 1
  • Comments: 19 (9 by maintainers)

Most upvoted comments

I’m seeing this same issue. From tcpdump, it looks like host is making 3 requests:

29611 1/13/11 A 216.58.216.14 (925)
 11068+ A? etcd.marathon.mesos. (37)
 11068* 1/0/0 A 172.16.31.218 (72)
 38364+ AAAA? etcd.marathon.mesos. (37)
 38364* 0/0/0 (37)
 52541+ MX? etcd.marathon.mesos. (37)
 52541 NXDomain* 0/1/0 (115)

Looks like NXDomain on the mail record is messing with host. host -t A master.mesos works fine, as expected.

I have no clue what the right solution here would be. It seems like its not a problem with mesos-dns unless you want to start emailing your service endpoints?