Piste Basher wrote:
However, whilst testing this with a device I have on LAN5, with a 192.168.5.x address supposedly bound to its MAC, I set the device to use DHCP, which I hadn't done before. It immediately dropped its LAN5 address and picked up a 192.168.1.x address :shock:

Wouldn't you get that effect, if a Port was a member of multiple Lans/VLANs and Tags were not in use (i.e. Port-based vlan). There seems to be nothing to stop such a configuration, but the DHCP server would have no idea which VLAN the client thought it was a member of...

https://draytek.co.uk/support/guides/kb-vigor-8021qvlan?highlight=WyJ2bGFuIl0=&return=19569888

(I've only used tagged VLANs - and I tag everything - using Netgear Switches upstream to sort out the problems that causes )

Hmm - it is the case that LAN5 is untagged. I guess I fondly imagined that, with the client MAC bound to a LAN5 address, the router would know it was a member of LAN5. Seems it doesn't work that way.

Why not simply set the client to the fixed dns?