In any case, after the installation, the router isn’t serving thegettys.net in its dns search path.
I’m not 100% sure about this though.
That said, I personally find it confusing to have three entirely separate namespaces AND databases for dns (.local, .lan, and whatever you use as your main domain), and would prefer NOT to continue using .lan after converting to a real domain such as thegettys.net.
.lan cannot be published to the main dns, among other problems.
Similarly, the proper usage of the subdomain system and views basically makes the idea of gw.hm.thegettys.net sanest - where thegettys.net is a dns server and web server located in the cloud, and hm.thegettys.net is the one located on the gateway. This eliminates hits to the main dns server(s) and simplifies view management.
and have that work
these days multiple browsers try to substitute solutions to the above.
Secondly, whatever we go with should be constant, not exposed to the outside world, and not possible to override with other configuration changes. Or so sayeth Jim.