Roland,
I agree that registering the hostname is not the problem. I have monitored the control GUI for my router and witnessed the Qlustar Head node name being automatically registered by the router when the computer reboots after Qlustar install. I tested with dig repo.qlustar.com as you suggest. First test is immediately after a fresh install and login as root. Result is:
connection timed out; no servers could be reached
The /usr/sbin/qlustar-initial-config script fails every call to the repo. If I then start the network service with;
service systemd-resolved start
Then the dig repo.glustar.com test succeeds. Here is an excerpt from the output:
Got Answer: Header opcode: Query, status=NoError, id: 57624 . . . repo.qlustar.com 0 IN A 192.168.55.113 Server: 127.0.0.53#53(127.0.0.53) . Msg Size: recvd: 61
So, that communication looks fine, and if I then proceed with the initial config script, it runs to completion with no errors, and no faults. There is a message at the end of the initial config script that the computer needs to be rebooted to proceed. I have learned from experience that if I reboot the computer at that point, there is no internet connection after the reboot, and I have not been able to restore that. I can't proceed with getting the one-time token and installing qluman-qt. I will read up on http proxy thing and if I find evidence of that being in place, I'll include that info in a re-install and see what we get. I will also see if I can ctl-c exit out of the "Press Return to Reboot" instruction at the end of the initial-config script, then try getting the one-time token, and get QluMan GUI installed while I still have internet connection, and then doing the reboot. Maybe that will get me a little further down the road. Thank you for the patience with whatever it is that is putting a wrench in the works here. You are kind to hang in there with me.
Kim