2
Help! DNS A Records only ones getting filtered. (lemmy.world)
submitted 5 months ago by Bluesheep@lemmy.world to c/selfhosted@lemmy.world
5 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.

top 5 comments
sorted by: hot top controversial new old
[-] hemmes@lemmy.world 0 points 5 months ago

How exactly are you testing this from your client, with ping? What are you using to query the DNS?

If you run nslookup from the client

  • Does the ‘server’ command return the correct DNS server?
  • Does .lan return the expected record?

I’m assuming you’ve run ifconfig to verify your client’s NIC has been assigned the correct DNS via DHCP?

[-] Bluesheep@lemmy.world 0 points 5 months ago

Thanks for replying, I appreciate the response.

I’m running dig @192.168.0.249 study.lan from my client (a MacBook).

If I run ‘dig @192.168.0.249 study.lan TXT’ I get a correct response (I have added a txt record)

If I run ‘dig @192.168.0.249 lan SOA’ or ‘NS’ I correctly get the records for the zone.

I think this eliminates the possibility of it being a routing error?

[-] hemmes@lemmy.world 0 points 5 months ago* (last edited 5 months ago)

Yeah if you can dig a record and received a response it’s not a routing issue.

But aren’t you on the same subnet as your DNS server? There’s no routing happening if you’re on the same subnet which I was assuming.

Even through dig defaults to outputting A records when no other options are specified, I would use the A option anyway just in case:

dig @192.168.0.249 study.lan A

If you use “ping study.lan” do you see it output the A record IP address in the first line of output?

Did you try using nslookup as I described?

[-] Bluesheep@lemmy.world 1 points 4 months ago

I switched out the router and things started working. Very weird, but I can’t tho jot anything other than it being the Virgin Media hub not liking it. Apparently they have history on this.

[-] hemmes@lemmy.world 1 points 4 months ago

Very strange, but glad you worked it out!

I’ll keep this thread in mind if I ever run into something similar.

this post was submitted on 07 Feb 2025
2 points (100.0% liked)

Selfhosted

48610 readers
484 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz