Comment

Comment on Help! DNS A Records only ones getting filtered.

truthfultemporarily@feddit.org ⁨2⁩ ⁨months⁩ ago

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.

source

Sort:hotnew top

possiblylinux127@lemmy.zip ⁨2⁩ ⁨months⁩ ago
You also could do nslookup on Windows

source
- hemmes@lemmy.world ⁨2⁩ ⁨months⁩ ago
  nslookup is available on macOS and most Linux distros as well (and very helpful indeed).
  
  source
  - possiblylinux127@lemmy.zip ⁨2⁩ ⁨months⁩ ago
    Don’t you mean dig
    
    source
    hemmes@lemmy.world ⁨2⁩ ⁨months⁩ ago
    Well, dig is available also of course, but nearly all distros still include nslookup despite it getting deprecated. I like the simplicity of its interactive mode.
    
    Host is also really great with more human-readable output.
    
    Don’t get me wrong, when things are getting hairy, you’re going to make a lot of use of dig. I just find that most troubleshooting can be taken care of a lot simpler with host or nslookup.
    
    source
Bluesheep@lemmy.world ⁨2⁩ ⁨months⁩ ago
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?

source
- truthfultemporarily@feddit.org ⁨2⁩ ⁨months⁩ ago
  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?
  
  source
  - Bluesheep@lemmy.world ⁨2⁩ ⁨months⁩ ago
    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.
    
    source
    truthfultemporarily@feddit.org ⁨2⁩ ⁨months⁩ 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?
    
    source