You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
I got {"message":"name resolution failed"} from Kong when my upstream had a localhost target.
This seems to be because my /etc/hosts is empty. However it should have worked:
From RFC 6761: Section 6.3.3
Name resolution APIs and libraries SHOULD recognize localhost
names as special and SHOULD always return the IP loopback address
for address queries and negative responses for all other query
types. Name resolution APIs SHOULD NOT send queries for
localhost names to their configured caching DNS server(s).
The text was updated successfully, but these errors were encountered:
I got
{"message":"name resolution failed"}
from Kong when my upstream had alocalhost
target.This seems to be because my /etc/hosts is empty. However it should have worked:
From RFC 6761: Section 6.3.3
The text was updated successfully, but these errors were encountered: