Able to access ProxMox by IP but not be localhost.localdomain as it was at install

[sorhan01]

first and foremost, if I'm not in the right place, please direct me to the right place.

When I installed ProxMox a few weeks ago, I could access it via https://localhost.localdomain.com:8006. At some point however that name quit working and it was only accessible by IP. I'm not sure where this name is published to my local DNS server, so I'm not sure what to check. I am assuming that this happened in regards to having to swap out routers, though this assumption may be wrong.

Any and all assistance greatly appreciated.

 

[fba]

Either add an entry for that name to your DNS server or add it locally at the computer you're using for the access (in file /etc/hosts on Linux, in file C:\Windows\System32\Drivers\etc\hosts on Windows)
The name by itself is of your free choice, but localhost.localdomain is usually used for local access (same host as you're working on) only. Don't use it for remote access, but choose something else.
By the way, whats the output of command hostname on the Proxmox host?

 

[sorhan01]

Thanks for the info, that is rather what I thought was going to be needed to rectify the situation, I did change routers, so it would make sense that any entry in the DNS there would have been lost in such.

I would like to confirm though that during the initial setup of Proxmox the DNS entry is created/registered/etc, Suspect that this is true as the services were accessible by localhost.localdomain(.com):8006 from the local network initially.

 

[sorhan01]

It looks like my understanding may have been greatly flawed. I probably needed to update the hosts file on the proxmox host after the network changes with a new IP address. Would not have thought this would have made a difference on the local network, however will be testing this out and confirming what the malfunction is.

 

[fba]

Well, an up-to-date /etc/hosts at the PVE really helps.
Even so it is not responsible for DNS resolution of a peer.