I think you’ve got the key point here. Most of the commentary on AI focuses on its impact on people that are already good at their jobs. Where I see it having most impact is for people who aren’t good or aren’t capable. It doesn’t make them a good coder, but it might make them a bit better than before.

The same is true for professional and technical writing. There may be an explosion of people ‘delving’ into topics, littered with em-dashes, and it might take them a while to produce it, but the principle time saving is that I’m not reviewing and editing all the garbage the first time round.

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.

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.

Thanks for the suggestion, I’ll grab a cap to check.

I’m running tcpdump -i any port 53. I can see the outbound request but not the reply. Will the cap show me anything more?

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?

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?