Comment

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

Bluesheep@lemmy.world ⁨1⁩ ⁨week⁩ 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?

Sort:hotnew top

hemmes@lemmy.world ⁨1⁩ ⁨week⁩ 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 <a-record>.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?
source
- Bluesheep@lemmy.world ⁨1⁩ ⁨week⁩ 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.
  
  source
  - hemmes@lemmy.world ⁨1⁩ ⁨week⁩ ago
    Very strange, but glad you worked it out!
    
    I’ll keep this thread in mind if I ever run into something similar.
    
    source