Comment 2 for bug 1753493

I can confirm this issue in 2.3. I have tested with 2 region/racks, and the output in 2.3 is:

           option domain-name-servers 10.90.90.1, 10.90.90.3;

The output in 2.4 is:

           option domain-name-servers 10.90.90.1, 10.90.90.1;

In my case 10.90.90.1 is the primary region/rack. It seems it is correctly adding a secondary entry for the secondary region/rack controller, but it is not considering the IP facing the machines as secondary.

In my environment, I'm forcing secondary rackd.conf to also point to 10.90.90.1 (e.g. as if it was a VIP), and in 2.3 is handled it correctly and 2.4 is not. So if I were to have a VIP of 10.90.90.100 this should be:

           option domain-name-servers 10.90.90.100, 10.90.90.1, 10.90.90.3;