Selfhosted

60758 readers

173 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

Help! DNS A Records only ones getting filtered. (lemmy.world)

submitted 1 year ago by Bluesheep@lemmy.world to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

I’m pulling my hair out over this. I’ve got a proxmox homelab, an LXC running technitium installed from TTeck’s script.

The DNS server is also doing DHCP for my network. I have an authoritative zone for ‘.lan’

I can get NS, SOA, TXT records from the DNS server, but no A records! The DNS query logs show that it gives an answer, and if I am on the DNS server itself I get an answer, but no other machines on the network hear the reply.

I think this means the DNS server is working properly. There are no FWs in the way as I can resolve other types.

Where else can I look, or how can I diagnose this? I am completely at a loss.

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

[–] truthfultemporarily@feddit.org 7 points 1 year ago* (last edited 1 year ago) (8 children)

Here is how I would diagnose (I'm assuming you have Linux / WSL on a client)

Check the DNS record is actually set (yes do it again)
Do these steps on the client:
dig $domain check which server answered
dig a $domain should give a record
dig a $domain @server to make sure you're querying the right server

If none work, probably network issue (DNS boind to wrong IP, firewall, etc)

If 3 and 5 work but 4 doesn't, your DNS isn't authorative.

If only 5 works DNS settings on the client is wrong.

[–] Bluesheep@lemmy.world 2 points 1 year ago (3 children)

Thanks for giving it some thought!

I have been testing using dig @192.168.0.249 study.lan

3, 4, and 5 work for TXT, NS and SOA but doesn’t work for A records. I think this rules out a simple network issue?

[–] truthfultemporarily@feddit.org 2 points 1 year ago (2 children)

Just to be sure you do dig A @server $domain (with the "A") and can confirm the following

SERVER is your server

;; ANSWER SECTION is empty (or doesn't exist)

;; AUTHORITY SECTION mentions your local DNS server

Also check

dig NS @server $domain

Is your server in the answer section?

[–] Bluesheep@lemmy.world 1 points 1 year ago (1 children)

Yes, everything looks right. I moved dhcp resolution from the router to technitium recently, but hadn’t set up local resolution.

I’m currently thinking the router is the culprit. Here in the UK there are lots of forum posts complaining about the Virgin Media gear. Nothing specifically describes my problem but I’m going to try a new router over the weekend.

[–] truthfultemporarily@feddit.org 2 points 1 year ago

Seems weird to me, the router would need to do deep packet inspection of DNS and selectively block specific ones. It feels more like you've set up your DNS to do forwarding instead of resolution. Can you post a network diagram and the DNS config?

load more comments (4 replies)