Description of problem:

Satellite server configures DNS servers per subnet rather than per domain per location.

Here's a use case to describe the problem.

User 1 wants a RHEL7 server on subnet 10.1.1.0/24 in the foo.com domain. His DNS servers are defined by the ones in the subnet as configured in the Satellite Server.

User 2 wants a RHEL7 server on subnet 10.1.1.0/24 in the bar.com domain. He cannot use the DNS servers defined in the subnet because those DNS servers are in the foo.com domain.

I don't think the DNS servers should be assigned by the domain rather than the subnet either. If the domain foo.com is valid in 7 datacenters around the globe, I need to be able to define two DNS servers for each domain in each site for performance and fault tolerance. In my case, I would provide a primary DNS server in the local datacenter, and a secondary DNS server in the closest remote datacenter.

I think the DNS servers need to be a property of the SITE. This is the only way I can see (in my use case) that I will get the flexibility to use the subnet for more than one domain. Otherwise I have to re-write the interface config file for each deployment.