numa.toml #81

New Issue

2026-04-12T04:00:04+08:00

bcookatpcsd commented

2026-04-12 04:00:04 +08:00

(Migrated from github.com)

Looks good

Just got it going..

touch .config/numa/numa.toml

 2. Run on a non-privileged port for testing.
       Create ~/.config/numa/numa.toml with:

         [server]
         bind_addr = "127.0.0.1:5354"
         api_port  = 5380

       Then run:  numa
       Test with: dig @127.0.0.1 -p 5354 example.com

then

~# ./numa
[2026-04-11T19:54:23.762Z INFO  numa::config] config not found, using defaults (create /var/lib/numa/numa.toml)
[2026-04-11T19:54:23.762Z INFO  numa::system_dns] detected system upstream: 192.168.88.252
[2026-04-11T19:54:23.762Z INFO  numa::system_dns] forwarding .onsite to 169.254.169.253
[2026-04-11T19:54:23.762Z INFO  numa::system_dns] detected 1 search domain forwarding rules
[2026-04-11T19:54:23.763Z INFO  numa::tls] loaded CA from "/var/lib/numa/ca.pem"
[2026-04-11T19:54:23.763Z INFO  numa::tls] generated TLS cert for: numa.numa
[2026-04-11T19:54:23.763Z INFO  numa::tls] TLS configured for 1 .numa domains

Numa — cannot bind to 0.0.0.0:53: port 53 is already in use.


then

./numa

[2026-04-11T19:57:30.873Z INFO numa::system_dns] detected system upstream: 192.168.88.252
[2026-04-11T19:57:30.873Z INFO numa::system_dns] forwarding .onsite to 169.254.169.253
[2026-04-11T19:57:30.873Z INFO numa::system_dns] detected 1 search domain forwarding rules
[2026-04-11T19:57:30.873Z INFO numa::tls] loaded CA from "/var/lib/numa/ca.pem"
[2026-04-11T19:57:30.874Z INFO numa::tls] generated TLS cert for: numa.numa
[2026-04-11T19:57:30.874Z INFO numa::tls] TLS configured for 1 .numa domains

╔══════════════════════════════════════════╗
║ NUMA DNS that governs itself v0.12.0 ║
╠══════════════════════════════════════════╣


it didn't seem to look in ~/.config/numa/

https://github.com/razvandimescu/numa/blob/main/numa.toml

This looks great..

Looks good Just got it going.. touch .config/numa/numa.toml ``` 2. Run on a non-privileged port for testing. Create ~/.config/numa/numa.toml with: [server] bind_addr = "127.0.0.1:5354" api_port = 5380 Then run: numa Test with: dig @127.0.0.1 -p 5354 example.com ``` then ``` ~# ./numa [2026-04-11T19:54:23.762Z INFO numa::config] config not found, using defaults (create /var/lib/numa/numa.toml) [2026-04-11T19:54:23.762Z INFO numa::system_dns] detected system upstream: 192.168.88.252 [2026-04-11T19:54:23.762Z INFO numa::system_dns] forwarding .onsite to 169.254.169.253 [2026-04-11T19:54:23.762Z INFO numa::system_dns] detected 1 search domain forwarding rules [2026-04-11T19:54:23.763Z INFO numa::tls] loaded CA from "/var/lib/numa/ca.pem" [2026-04-11T19:54:23.763Z INFO numa::tls] generated TLS cert for: numa.numa [2026-04-11T19:54:23.763Z INFO numa::tls] TLS configured for 1 .numa domains Numa — cannot bind to 0.0.0.0:53: port 53 is already in use. ``` ``` then ``` # ./numa [2026-04-11T19:57:30.873Z INFO numa::system_dns] detected system upstream: 192.168.88.252 [2026-04-11T19:57:30.873Z INFO numa::system_dns] forwarding .onsite to 169.254.169.253 [2026-04-11T19:57:30.873Z INFO numa::system_dns] detected 1 search domain forwarding rules [2026-04-11T19:57:30.873Z INFO numa::tls] loaded CA from "/var/lib/numa/ca.pem" [2026-04-11T19:57:30.874Z INFO numa::tls] generated TLS cert for: numa.numa [2026-04-11T19:57:30.874Z INFO numa::tls] TLS configured for 1 .numa domains ╔══════════════════════════════════════════╗ ║ NUMA DNS that governs itself v0.12.0 ║ ╠══════════════════════════════════════════╣ ``` it didn't seem to look in ~/.config/numa/ https://github.com/razvandimescu/numa/blob/main/numa.toml This looks great..

razvandimescu commented

2026-04-12 07:16:34 +08:00

(Migrated from github.com)

Thanks @bcookatpcsd reporting this and for the log, it was a mismatch between the port-53 advisory and what load_config actually reads.
On interactive root, config_dir() routed to /var/lib/numa/
while the advisory hardcoded ~/.config/numa/numa.toml so the file you created was never consulted.
Fix in #83: advisory now prints the real path, and load_config consults $HOME/.config/numa/numa.toml too.
Interactive root should now work as advertised

Thanks @bcookatpcsd reporting this and for the log, it was a mismatch between the port-53 advisory and what load_config actually reads. On interactive root, config_dir() routed to /var/lib/numa/ while the advisory hardcoded ~/.config/numa/numa.toml so the file you created was never consulted. Fix in #83: advisory now prints the real path, and load_config consults $HOME/.config/numa/numa.toml too. Interactive root should now work as advertised

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/numa#81