Hey guys,
I’m having DNS resolution issues when setting up a new upstream for my API. Here is the health endpoint return value for the upstream:
/ # curl -i localhost:8001/upstreams/ffad1073-40ed-4a2d-885d-2ef1d4c17bd9/health
HTTP/1.1 200 OK
Date: Mon, 09 Jul 2018 16:15:45 GMT
Content-Type: application/json; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Access-Control-Allow-Origin: *
Server: kong/0.13.1
{"total":1,"data":[{"created_at":1531151765344,"health":"DNS_ERROR","id":"10ec2ad6-6e6f-42ef-b55d-3a006b177fa5","upstream_id":"ffad1073-40ed-4a2d-885d-2ef1d4c17bd9","target":"tusd.roseau:1080","weight":100}],"node_id":"67168b57-28c5-40ff-84dc-f2693711d232"}
Along with a curl request to the configured DNS which works as expected:
/ # curl -i tusd.roseau:1080
HTTP/1.1 200 OK
Date: Mon, 09 Jul 2018 16:15:52 GMT
Content-Length: 729
Content-Type: text/plain; charset=utf-8
So i’m not sure why Kong is not able to resolve the DNS when using Upstream. It works well if i’m configuring the API to directly point to http://tusd.roseau:1080 instead of my upstream.
Any ideas?
I’m using kong 0.13.1