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

Don't use public gateway for DNS lookups "automatic mode" is off #916

Open
Stebalien opened this issue Aug 19, 2020 · 2 comments
Open

Don't use public gateway for DNS lookups "automatic mode" is off #916

Stebalien opened this issue Aug 19, 2020 · 2 comments
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked
Milestone
v2.21

Comments

@Stebalien
Copy link
Member

I'd like IPFS companion to use a local gateway without exposing a local IPFS API endpoint. Unfortunately, if I do this, companion will direct all dnslink queries to the public gateway because my local IPFS node "has no peers".

If I configure companion to use a specific IPFS gateway, I expect it to always use that gateway.
@Stebalien Stebalien added the need/triage Needs initial labeling and prioritization label Aug 19, 2020
@jessicaschilling
Copy link
Contributor

Thanks @Stebalien -- we'll bring this up in our next weekly triage session.

@lidel
Copy link
Member

lidel commented Aug 25, 2020

SGTM, switching to gateway for dnslink lookups should work:
http://localhost:8080/api/v0/dns/docs.ipfs.io?cid-base=base32

@lidel lidel added P2 Medium: Good to have, but can wait until someone steps up exp/novice Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue status/ready Ready to be worked and removed need/triage Needs initial labeling and prioritization labels Aug 25, 2020
@lidel lidel added this to the v2.15 milestone Sep 6, 2020
@lidel lidel modified the milestones: v2.15, v2.16 Oct 19, 2020
@lidel lidel modified the milestones: v2.16, v2.17 Nov 18, 2020
@lidel lidel modified the milestones: v2.17, v2.18 Jan 11, 2021
@lidel lidel modified the milestones: v2.18, v2.21 Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P2 Medium: Good to have, but can wait until someone steps up status/ready Ready to be worked
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Needs Grooming
Milestone
v2.21
Development

No branches or pull requests
3 participants
@lidel @Stebalien @jessicaschilling