Skip to content

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

Description

@AchoArnold

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions