

1·
2 months agoThanks 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 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 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?
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.