Feature Request: Manage Known Hosts

Feature Requests
1

A fairly basic feature sorely missing from the Route10 is the ability to manage known hosts. I typically use custom host entries to redirect traffic to an internal host when hairpin NAT would otherwise occur. For example, I might run a speed test service on my network that is publicly accessible through a reverse proxy server at speedtest.domain.com. When attempting to access speedtest.domain.com from my LAN, I want it to resolve directly to the internal host IP, not my WAN IP, eliminating a hairpin NAT situation. Custom host entries can also be used as a DNS sinkhole.

I can manually add entries to /etc/hosts on my Route10, but I don’t want to layer CLI mods to my setup and the changes don’t persist after rebooting.

1 Like
2

I agree that this should be on the road map if it isn’t already. In the mean time I have

if [ "$(uci get dhcp.@dnsmasq[0].addnhosts)" != "/cfg/hosts" ]; then
    uci add_list dhcp.@dnsmasq[0].addnhosts='/cfg/hosts'
    uci commit
    /etc/init.d/dnsmasq reload
fi

called from my post-cfg.sh, and put entries in /cfg/hosts.

3 Likes