AWS Client VPN sets a hostname

VPN
1

When I connect to a client VPN endpoint, I notice the hostname on my laptop is changed to an IP-address-based hostname similar to what an EC2 instance would have. Eg

ip-192-168-0-100.us-west-2.compute.internal

A few problems with this, I guess the most important is that I prefer not to have the hostname changed at all. We are split tunnel and the inbound clients are passing through a NAT (right?) so it seems fine to leave hosts named what the end user has chosen for their home network. However I don’t know how to suppress the renaming with the AWS VPN client software.

(And furthermore, that IP address isn’t even relevant- it’s not the client IP for this connection which at least would be helpful but still not what I want)

Any pointers much appreciated.

Thanks!

2

Yeah I get the same thing and it’s annoying. The only thing I thought of to do was write some tunnelblick scripts to fix my hostname.

3

Oh, I got an answer on the https://repost.aws forum. Apparently the hostname sent from the server should not override one that is locally set.

On macOS that means we have to “scutil —set HostName” which we now do as part of the desktop provisioning step, and the client VPN doesn’t override that going forward.