Dynamic DNS - Revision history

MiniBill: Non-hardware configuration should go in configuration.nix

2026-03-30T13:13:08Z

Non-hardware configuration should go in configuration.nix

← Older revision		Revision as of 13:13, 30 March 2026
Line 9:		Line 9:
	One easy to setup DNS updater is [https://github.com/qdm12/ddns-updater ddns-updater]. It may be configured like so:		One easy to setup DNS updater is [https://github.com/qdm12/ddns-updater ddns-updater]. It may be configured like so:

	{{file\|/etc/nixos/~~hardware-~~configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
	services.ddns-updater = {		services.ddns-updater = {
	enable = true;		enable = true;

Klinger: Category:DNS added

2025-12-28T12:47:44Z

Category:DNS added

← Older revision		Revision as of 12:47, 28 December 2025
Line 46:		Line 46:

	[[Category:Networking]]		[[Category:Networking]]

			[[Category:DNS]]

Klinger: Category:Networking added

2025-12-28T12:47:11Z

Category:Networking added

← Older revision		Revision as of 12:47, 28 December 2025
Line 44:		Line 44:

	You can verify proper operation using <code>journalctl -u ddns-updater.service</code>. Note that previous manual DNS entries might not be overwritten using this tool and need to be deleted first.		You can verify proper operation using <code>journalctl -u ddns-updater.service</code>. Note that previous manual DNS entries might not be overwritten using this tool and need to be deleted first.

			[[Category:Networking]]

Onny: /* Confiuration example */

2025-12-06T23:19:58Z

Confiuration example

← Older revision		Revision as of 23:19, 6 December 2025
Line 22:		Line 22:
	Where <code>CONFIG_FILEPATH</code> should correspond to the location of your config.json file.		Where <code>CONFIG_FILEPATH</code> should correspond to the location of your config.json file.

	The following is an example for Porkbun. Consult the documentation of your DNS provider for proper formatting and make sure to enable API access if needed.		The following is an example for the provider [https://porkbun.com Porkbun]. Consult the documentation of your DNS provider for proper formatting and make sure to enable API access if needed.

	{{file\|config.json\|json\|<nowiki>		{{file\|config.json\|json\|<nowiki>

Onny: /* Confiuration example */

2025-12-06T23:18:50Z

Confiuration example

← Older revision		Revision as of 23:18, 6 December 2025
Line 16:		Line 16:
	CONFIG_FILEPATH = "/etc/ddns-updater/config.json";		CONFIG_FILEPATH = "/etc/ddns-updater/config.json";
	PERIOD = "5m";		PERIOD = "5m";
			};
	};		};
	</nowiki>}}		</nowiki>}}

Onny: /* Confiuration example */

2025-12-06T23:18:31Z

Confiuration example

← Older revision		Revision as of 23:18, 6 December 2025
Line 10:		Line 10:

	{{file\|/etc/nixos/hardware-configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/hardware-configuration.nix\|nix\|<nowiki>
	services.ddns-updater.enable = true;		services.ddns-updater = {
	~~services.ddns-updater.~~environment = {		enable = true;
	SERVER_ENABLED="no";		environment = {
	CONFIG_FILEPATH = "/etc/ddns-updater/config.json";		SERVER_ENABLED="no";
	PERIOD = "5m";		CONFIG_FILEPATH = "/etc/ddns-updater/config.json";
	};		PERIOD = "5m";
			};
	</nowiki>}}		</nowiki>}}

Line 27:		Line 28:
	{		{
	"provider": "porkbun",		"provider": "porkbun",
	"domain": "~~1234567890abcdefg1234567890~~",		"domain": "example.org",
	"api_key": "pk1_1234567",		"api_key": "pk1_1234567",
	"secret_api_key": "1234567890abcdefg1234567890"		"secret_api_key": "1234567890abcdefg1234567890"
Line 33:		Line 34:
	{		{
	"provider": "porkbun",		"provider": "porkbun",
	"domain": "subdomain.~~domain~~.~~example~~",		"domain": "subdomain.example.org",
	"api_key": "pk1_1234567890abcdefg1234567890",		"api_key": "pk1_1234567890abcdefg1234567890",
	"secret_api_key": "sk1_1234567890abcdefg1234567890"		"secret_api_key": "sk1_1234567890abcdefg1234567890"

Arnecc: Created page with "[https://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] (DDNS) is a method that automatically updates name server records with current information such as hostnames and IP addresses. This is particularly useful for users hosting services on a home network with a dynamic public IP address, which can change over time due to ISP policies or network restarts. By using DDNS, users can maintain consistent access to their services over the internet via a fixed domain name, eve..."

2025-12-06T22:34:14Z

Created page with "[https://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] (DDNS) is a method that automatically updates name server records with current information such as hostnames and IP addresses. This is particularly useful for users hosting services on a home network with a dynamic public IP address, which can change over time due to ISP policies or network restarts. By using DDNS, users can maintain consistent access to their services over the internet via a fixed domain name, eve..."

New page

[https://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] (DDNS) is a method that automatically updates name server records with current information such as hostnames and IP addresses. This is particularly useful for users hosting services on a home network with a dynamic public IP address, which can change over time due to ISP policies or network restarts.

By using DDNS, users can maintain consistent access to their services over the internet via a fixed domain name, even as their IP address changes. The DDNS client software or service detects IP changes and promptly updates the DNS records to ensure reliable remote connectivity.

There are [https://wiki.archlinux.org/title/Dynamic_DNS many] options to choose from, some are provider specific.

== Confiuration example ==

One easy to setup DNS updater is [https://github.com/qdm12/ddns-updater ddns-updater]. It may be configured like so:

{{file|/etc/nixos/hardware-configuration.nix|nix|<nowiki>
services.ddns-updater.enable = true;
services.ddns-updater.environment = {
SERVER_ENABLED="no";
CONFIG_FILEPATH = "/etc/ddns-updater/config.json";
PERIOD = "5m";
};
</nowiki>}}

Where <code>CONFIG_FILEPATH</code> should correspond to the location of your config.json file.

The following is an example for Porkbun. Consult the documentation of your DNS provider for proper formatting and make sure to enable API access if needed.

{{file|config.json|json|<nowiki>
{
"settings": [
{
"provider": "porkbun",
"domain": "1234567890abcdefg1234567890",
"api_key": "pk1_1234567",
"secret_api_key": "1234567890abcdefg1234567890"
},
{
"provider": "porkbun",
"domain": "subdomain.domain.example",
"api_key": "pk1_1234567890abcdefg1234567890",
"secret_api_key": "sk1_1234567890abcdefg1234567890"
}
]
}
</nowiki>}}

You can verify proper operation using <code>journalctl -u ddns-updater.service</code>. Note that previous manual DNS entries might not be overwritten using this tool and need to be deleted first.