Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dial tcp: lookup topups.reloadly.com on 169.254.169.254:53: no such host #11

Open
AchoArnold opened this issue Feb 13, 2022 · 0 comments
Open

dial tcp: lookup topups.reloadly.com on 169.254.169.254:53: no such host #11

AchoArnold opened this issue Feb 13, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@AchoArnold
Copy link

Describe the bug

No TCP connection to reloadly domain

Expected Behavior

DNS should always be resolved

Current Behavior

When makeing a request to the reoloadly domain name, I usually get errors about the DNS not being resolved. The error looks like this

Get "https://topups.reloadly.com/topups/reports/transactions/5593913": dial tcp: lookup topups.reloadly.com on 169.254.169.254:53: no such host

Steps to Reproduce

Repeatedly make a request to topups.reloadly.com

Possible Solution

DNS resolution should always work

Context

I'm trying to do a topup or also trying to iew a transaction

Your Environment

Google cloud RUN
@AchoArnold AchoArnold added the bug Something isn't working label Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AchoArnold