DNS name changed

1

Hi Team.

I have an issue where my network team changed DNS name of the BigFix Server without discussing it with me.
The result is that now my SandBox BigFix Server (Test) is a piece of brick. Not possible to connect new clients.

Is there any chance that i can “Manually” connect at least 1 client?
I know the whole procedure to request new licence file and make a BigFix Server set up from scratch.

But is it possible to connect at least one client manually?

Best regards,
Anton

2

Well, haven’t tested but see to edit the client’s hosts file to point to the IP of the BigFix server, that may just “fake” enough the host being the same as before and allow it to report to it.

1 Like
3

Not really. Client tries to register with the link for old DNS name.
changing manually link in the mastheadfor installation is just failing mashead load after install.
And fixing reg keys for client also does not make difference.

PS. I got it. just add “old” name with correct IP into the HOTST.

I will try that

1 Like
4

OK. Reported. Thank you.

1 Like
5

Another option is to add a ‘Last Fallback Relay’ to the masthead (via BESAdmin) that references the new DNS name, and then replace the masthead file on Clients with the updated version of the masthead. See https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Config/c_editing_the_masthead.html for details.

3 Likes
6

It’s also common to add an alias ( CNAME ) entry to DNS to point the BigFix service name to server.

Ideally one would create a masthead with a generic name like ‘bigfix.company com’.
When hosted on a unique server like Loc1Server23456.region.company com, use a DNS alias to point ‘bigfix.company com’ to that server.
Server upgrades/migrations become a lot easier then - just build a new server, restore BigFix databases, and then change the DNS alias to point at the new server.

4 Likes