I’m trying to wrap my head around how that will work though. What would be ideal is to use a DNS entry called fog and it uses the local fog server, however, I can’t think of a way to tell DNS to only give a local A record for “fog”. I guess I should have been more clear, multiple sites, all same domain. Each site has it’s own fog server, and domain/dns server. With DNS being AD integrated it replicates all entries, helpful in most cases except this, where I don’t want it replicated

I wonder if I create a new zone, not stored in AD, and then point it there. Maybe a fog.local zone, then create the same zone on all the servers, with an A record for the local fog server.

We have multiple fog servers spread across multiple sites. We generally create an image on a single server, then copy that image to the other servers and set up the database entry. The issue this causes is the fog client then points back to a single server that does not know about the host if the host was imaged by an offsite fog server.

I’m looking for a way to basically put a dns entry or something in the the fog server entry and have it pull from dhcp or dns what server to talk to and was wondering if anyone has come across anything similar?

I’m not looking to use the centralized fog server approach with storage nodes. We’ve done that in the past and prefer to keep things separate.