group and agent.circuit-id

[Niall O'Reilly]

On 3 Dec 2016, at 5:59, Nick Urbanik wrote:

> class "a-particular-agent.circuit-id" {
>    match if option agent.circuit-id = "a-particular-agent.circuit-id";
>    option domain-name-servers 1.2.3.4, 5.6.7.8;
> }
> class "another-particular-agent.circuit-id" {
>    match if option agent.circuit-id = 
> "another-particular-agent.circuit-id";
>    option domain-name-servers 1.2.3.4, 5.6.7.8;
> }
> ...
> Would that work?

   Yes, but using subclasses (Droms & Lemon: The DHCP Handbook, 1st edn. 
p. 273)
   should be more efficient.

   For example:

   class "dns-by-circuit-id" {
     match option agent-circuit-id;
     option domain-name-servers 1.2.3.4, 5.6.7.8;
   }

   subclass "dns-by-circuit-id" "a-particular";
   subclass "dns-by-circuit-id" "a-nother";
   subclass "dns-by-circuit-id" "a-third" {
     # subclass can over-ride master class if necessary
     option domain-name-servers 2.3.4.5, 6.7.8.9;
   }

   Best regards,
   Niall O'Reilly