Howdy. I'm running Tomato 1.9 on a Linksys WRT54G v3. I'm attempting to redirect DNS on the LAN to use the private IP for a host, as opposed to having to go "out the front door" to hit internal machines. Initially, I added the proper line to /etc/hosts.dnsmasq, but it disappeared on reboot. The solution I came up with (and it may be heinously incorrect, if so tell me, please!) was to assign static DHCP leases to the proper MAC addresses (even though the machines in question have the IP hardcoded in). # cat /etc/dnsmasq.conf interface=br0 resolv-file=/etc/resolv.dnsmasq addn-hosts=/etc/hosts.dnsmasq expand-hosts dhcp-range=192.168.1.100,192.168.1.149,255.255.255.0,1440m dhcp-option=3,192.168.1.1 dhcp-authoritative dhcp-host=01:02:03:04:**:**,22.214.171.124 dhcp-host=00:1C:B3:C1:**:**,192.168.1.2,1440m dhcp-host=00:06:5BD:**:**,192.168.1.15,1440m dhcp-host=00:1D:60:92:**:**,192.168.1.20,1440m # cat /etc/hosts.dnsmasq 192.168.1.1 unknown 192.168.1.2 singularity.mydomain.com 192.168.1.15 alcatraz.mydomain.com 192.168.1.20 tempest.mydomain.com The issue occurs when I ssh into a box from 192.168.1.2, it shows the connection as coming from the tomato box itself: singularity:$ ssh firstname.lastname@example.org [jay@alcatraz ~]$ w 10:48PM up 1 day, 22:49, 1 user, load averages: 0.66, 0.26, 0.14 USER TTY FROM LOGIN@ IDLE WHAT jay p0 192.168.1.1 10:48PM - w [jay@alcatraz ~]$ Any idea why it's doing this? DNS resolvs properly to the internal IP for this host. Thanks in advance; let me know if I can provide any further information.