Forward DNS for Consul Service Discovery

[lens0021]

To use the Init Task Pattern of lifecycle Stanza, we need a forward DNS for Consul Service Discovery.

Reference(s)

• https://aws.amazon.com/premiumsupport/knowledge-center/dns-resolution-failures-ec2-linux/#Resolution

[lens0021]

Closed by femiwiki/infra@180ab0e

[lens0021]

dig @127.0.0.1 mysql.service.dc1.consul works but dig mysql.service.dc1.consul and ncat don't.

$ ncat --send-only mysql.service.dc1.consul < /dev/null; echo $?
Ncat: Could not resolve hostname "mysql.service.dc1.consul": Name or service not known. QUITTING.
2

[lens0021]

dnsmasq is re-deploy at femiwiki/infra@4cc5d42 and femiwiki/infra@0e0b953

[lens0021]

Today I tried to make systemd-resolved to achieve forwarding DNS but have never made nslookup consul.service.consul to succeed. Any try to make /etc/resolv.conf to include nameserver 127.0.0.1:8600 has failed.

As a workaround, nslookup -port=8600 consul.service.consul 127.0.0.1 can be used.¹ I will do that.

Footnotes

1. https://stackoverflow.com/a/63663167/10916512 ↩

[lens0021]

https://github.com/burdandrei/hcp-enabled-nomad/blob/main/user-data-client.sh ?