Selfhosted

60789 readers

307 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Routing local requests directly to server instead of cloudflare tunnel (feddit.de)

submitted 2 years ago* (last edited 2 years ago) by Scrath@feddit.de to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

Hey everyone, I wanted to ask for some help regarding my DNS setup and for routing requests to my selfhosted services.

Currently I use Pi-Hole as a DNS server with my routers default DNS server as the upstream server. This allowed me to define local DNS entries using Pi-hole and route my requests to these domains directly to my local services. For example I bought a domain a while ago and in preparation for setting it up, I had it entered as a local DNS entry pointing directly to my servers IP address.

Earlier today I finally got around to setting up a cloudflare tunnel to expose one of my services to the outside world using the domain I bought. Ever since I did that, all requests to that domain seem to exit my home network, go through cloudflares network and then return through the tunnel, even though I have a local DNS entry for that domain name.

What I would prefer is for the request to be routed directly to my server instead, since I am in the same network already. Since my DNS server is the Pi-Hole, I figured this should happen automatically.

Is there an issue with my Pi-Hole setup? If there is any information missing I'll be happy to provide it. I wasn't sure what information I could safely post here.

Solution

I think I managed to fix the problem. After enabling the option Never forward reverse lookups for private IP ranges in Pi-Hole and clearing my DNS cache again, nslookup only returns local IP addresses instead of the IPv6 address of two cloudflare servers.

you are viewing a single comment's thread
view the rest of the comments

[–] Scrath@feddit.de 1 points 2 years ago* (last edited 2 years ago)

Looking at the output of that command I get the following for my ethernet network interface

DNS-Server  . . . . . . . . . . . : fd98:1919:5915:0:3053:4134:bdc9:295d
                                          192.168.1.60
                                           fd98:1919:5915:0:3053:4134:bdc9:295d

Using nslookup on that IPv4 address tells me that all of those addresses are pointing to my pi-hole

nslookup 192.168.1.60

Server: pi.hole
Address: fd98:1919:5915:0:3053:4134:bdc9:295d

Name: pi.hole
Address: 192.168.1.60

I've added another local DNS entry on my Pi-Hole which points the domain I use to the same server but this time uses its IPv6 address. That doesn't seem to help though or it takes some time to update. I flushed the DNS cache on my machine after adding this entry though.