Fog client DNS name instead of IP

[wouwie]

Hi

Is it possible to use a DNS name in the IP address field when installing FOG Client?

I have 4 schools that will be connected with fiber within +/- 1 year.
Now there is no connection at all.

I’d like to use FOG server NOW in each school, but as soon as they are connected, I’d like to keep just one FOG server.
School 1: fog-server -> 10.1.0.111 (will remain)
School 2: fog-server -> 192.168.0.111 (wil be removed)
School 3: fog-server -> 10.4.0.111 (wil be removed)
School 4: fog-server -> 172.16.0.111 (wil be removed)

Is it possible and is it going to work, pointing it to another server (after manually importing all Hosts and transferring images to the 10.1.0.111 FOG server?)

[Wayne Workman]

@wouwie said in Fog client DNS name instead of IP:

Is it possible to use a DNS name in the IP address field when installing FOG Client?

Yes. Of course you need a DNS A record for the name pointing to the right IP in your DNS server.

Is it possible and is it going to work, pointing it to another server

Probably not - each fog server has a unique SSL certificate that the client anchors to. If that changes, the client will distrust the fog server. This is part of the security design. If all of the hosts in your environment are already working with the old FOG Servers, you’ll probably need to do a re-install to make them work with the new fog server.

Read this for more information: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

[wouwie]

OK, thanks!

Is there another solution?
I’m thinking of connecting the schools temporary with a OpenVPN and join them all together in one domain. So each location would still have a DC and file servers untill they are connected with fiber.

[george1421]

You can use a dns name and create a split horizion dns where you make fogserv.domain.com at each school point locally to the local fog server.

The issue is as Wayne said, Once the client touches a fog server it becomes tattooed to that fog server. Now if you know that ahead of time you can synchronize (i.e. copy the ssl certificate from your master FOG servers to the other remote fog servers) then have the clients reach out via dns name. If you have any clients that have touched one of the older non master fog server, you will have to reinstall the fog client on the target computer.