AdGuard Sync

This project will sync entries between two Primary and Secondary AdGuard Home instances using the API.

This is useful if you're dependent on local DNS and want to ensure relative High Availability.

How to Run

AdGuard Sync is packaged as a Docker image and can be ran anywhere with access to your instances. You can update the docker-compose.yaml file with your values based on the following:

Variable	Required	Description	Default
ADGUARD_PRIMARY	Yes	Primary base URL for the primary AdGuard instance (Ie. http://dns01.example.com)	N/A
ADGUARD_SECONDARY	Yes	Secondary base URL for the primary AdGuard instance (Ie. http://dns02.example.com)	N/A
ADGUARD_USER	Yes	Username to log into your AdGuard instances.	N/A
ADGUARD_PASS	Yes	Password to log into your AdGuard instances.	N/A
SECONDARY_ADGUARD_USER	No	Username to log into your secondary AdGuard instance. Only necessary if credentials are different between primary and secondary	Value of 'ADGUARD_USER'
SECONDARY_ADGUARD_PASS	No	Password to log into your secondary AdGuard instance. Only necessary if credentials are different between primary and secondary	Value of 'ADGUARD_PASSWORD'
REFRESH_INTERVAL_SECS	No	Frequency in seconds to refresh entries.	60

Once you've updated the file and ensure you have docker and docker-compose installed, run the following in the root directory:

docker-compose up -d

You can check on the status of your newly running pod with:

docker-compose logs

NOTE: The container is set to automatically restart when the docker daemon restarts.