Re: TigerVNC fails to display new windows properly
On Sun, 2019-05-19 at 14:23 -0400, Alex wrote:
The reason the hostname is displayed as
"localhost.localdomain" is
because it's on a private IP range (192.168.9.110) without DNS, and
I'm using port forwarding from the cable modem to this host for port
5900 through 6000.
I'm not sure if VNC will handle localhost being its hostname, it will
depend on how smart it is, or whether it bothers using hostnames.
localhost, and localhost.localdomain will normally resolve back to
127.0.0.1 (meaning "itself"). As such, connections may not get put
through to the remote side of things.
While some things will also add the local IP address to that line in
the /etc/hosts file, that can cause failures. The machine's hostname
should resolve to its real IP (the one that other devices can reach it
at).
You don't need to have a DNS server to resolve hostnames. You can add
it yourself to your /etc/hosts file (of course, you need to have a
fixed IP for this to be consistent).