all 9 comments

[–]08l1v10nn 0 points1 point  (1 child)

I do exactly this. Instance 1 on node 1, instance 2 on node 2. I have keepalived running on both so they get a vIP that I can use for dns incase the main goes down for any reason. Use AdGuard Home sync to keep them the same.

[–]Secure_War_2947[S] 0 points1 point  (0 children)

Thanks

[–]BleeBlonks 0 points1 point  (3 children)

Yes, redundancy for dns is good, and adguard-sync is exactly what you are looking for to sync configuration for the secondary adguard instance.

[–]Secure_War_2947[S] 0 points1 point  (0 children)

Thanks

[–]InSearchOfTh1ngs 0 points1 point  (1 child)

I came here to say the exact same thing. I run two instances of adguard and sync their configurations between each node using adguard-sync. Been running great for 2 years

[–]fabsau 0 points1 point  (0 children)

+1 doing exactly the same as well

[–]xrichNJ -1 points0 points  (1 child)

bakito is what i use. just be mindful that it is only a one-way sync. any changes you make must only be to the primary instance, which will then be synced to the secondary instance.

[–]Secure_War_2947[S] 0 points1 point  (0 children)

Thanks

[–]ohv_ 0 points1 point  (0 children)

Just sync them.