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.
nslookup is available on macOS and most Linux distros as well (and very helpful indeed).
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?
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
I’m assuming you’ve run ifconfig to verify your client’s NIC has been assigned the correct DNS via DHCP?
Very strange, but glad you worked it out!
I’ll keep this thread in mind if I ever run into something similar.