Comment on Help! DNS A Records only ones getting filtered.
hemmes@lemmy.world 1 week 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 <A-record>.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 1 week ago
Thanks for replying, I appreciate the response.
I’m running
dig @192.168.0.249 study.lanfrom 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 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?
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.
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.