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

• 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?