No, two of my computers are in the same LAN at home and another is at an IP that I know very well. This strange IP is located in Boulder, very far from me.
My other remote computer also connects to the strange IP.
So the DNS name doesn’t even resolve for me, there is something funky with your DNS to start with, so we can’t be for sure that the IP it’s showing is actually correct.
Also, it might connect to a different relay every time it starts so verify that it’s still the same relay you are joining.
My computer at work, which is at a different network, also connects to this server, accoring to netstat -W -A inet -p
I restarted syncthing at my work machine and now it connects to:
relay.ubiquitous.work:https ESTABLISHED 27071/syncthing
24hour-carfinance.org:22067 ESTABLISHED 27071/syncthing
The strange server seems to always connect.
Pinging 24hour-carfinance.org from the work computer fails, though, like for you. At home I have AT&T internet and ping shows the IP address.
DNS resolves for me, but slightly diff IP’s than OP gets. It’s probably just doing some anycast or geocasting tricks on the DNS (which is common for larger ISP’s and web hosting companies to do).
I’m almost positive this is just relaying… especially with the port being 22067.
In DNS it’s possible for the Netblock owner to specify a PTR record this is a reverse DNS lookup that means when you query a DNS server with an IP address an domain name is returned.
It’s possible the IP belonged to a connection associated with 24hour-carfinance.org at some-point in the past and no longer is, but the owner of the Netblock (Usually the ISP) hasn’t bothered to update/reset the PTR (RDNS) record to reflect that it no longer anything to do with that domain/customer.
I’ve seen that a few times with providers that allow you to change the RDNS entry to something custom. Since it doesn’t effect much (other than maybe mail delivery) it’s possible the new user hasn’t noticed or can’t be bothered to do anything about it.