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.

  • Bluesheep@lemmy.worldOPEnglish
    1·
    1 day 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.worldEnglish
      1·
      11 hours 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?