hashicorp / hashicorp/consul-aws

Only SRV records ?

Open
#25 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
55
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Hi,
Since the upgrade to 0.1.2, when I sync-catalog, my SRV records are created but I don't have any A record in route 53.

````
dig consul.sandbox

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-16.P2.el7_8.6 <<>> consul.sandbox
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4430
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;consul.sandbox. IN A

;; AUTHORITY SECTION:
sandbox. 579 IN SOA ns-1536.awsdns-00.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 2 msec
;; SERVER: 10.232.0.20#53(10.232.0.20)
;; WHEN: Wed Jul 29 17:50:16 UTC 2020
;; MSG SIZE rcvd: 130
````

````
dig srv consul.sandbox

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-16.P2.el7_8.6 <<>> srv consul.sandbox
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21020
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;consul.sandbox. IN SRV

;; ANSWER SECTION:
consul.sandbox. 1 IN SRV 1 1 8300 srv-kqxpnfnipvmxzb27_10.232.34.232_8300.consul.sandbox.
consul.sandbox. 1 IN SRV 1 1 8300 srv-kqxpnfnipvmxzb27_10.232.27.19_8300.consul.sandbox.
consul.sandbox. 1 IN SRV 1 1 8300 srv-kqxpnfnipvmxzb27_10.232.18.127_8300.consul.sandbox.

;; Query time: 2 msec
;; SERVER: 10.232.0.20#53(10.232.0.20)
;; WHEN: Wed Jul 29 17:51:50 UTC 2020
;; MSG SIZE rcvd: 264
````

````
curl consul.sandbox
curl: (6) Could not resolve host: consul.sandbox; Unknown error
````
Am I missing something ?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the sync-catalog path that creates Route 53 records, focusing on how SRV and A records are handled. Reproduce the report with the shown dig and curl commands, then verify that syncing produces an A record for consul.sandbox and that the hostname resolves.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
cloud, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.