SRTT only on address not upstream? #102

New Issue

2026-04-14T20:50:56+08:00

bcookatpcsd commented

2026-04-14 20:50:56 +08:00

(Migrated from github.com)

(thank you for all your attention)

1 -
[upstream] and address seems to work with multiple endpoints:

numa.toml example file:

# [upstream]
# mode = "forward"                              # "forward" (default) — relay to upstream
#                                               # "recursive" — resolve from root hints (no address needed)
# address = "9.9.9.9"                           # single upstream (plain UDP)
# address = ["192.168.1.1", "9.9.9.9:5353"]    # multiple upstreams — SRTT picks fastest

also numa.toml example file:

# [[forwarding]]                                    # DoT upstream: tls://IP[:port]#hostname
# suffix = ["google.com", "goog"]                   # hostname is the TLS SNI / cert name
# upstream = "tls://9.9.9.9#dns.quad9.net"          # port 853 default

doing an:

upstream = "tls://9.9.9.9:853#dns.quad9.net" , "tls://149.112.112.112:853#dns.quad9.net"

or

upstream = [ "tls://9.9.9.9:853#dns.quad9.net" , "tls://149.112.112.112:853#dns.quad9.net" ]

(assuming that the bootstrap'ing is not the problem)

2 -
(I also have these disabled while I'm working through the features and syntax)

[dot]
    enabled = false

[proxy]
    enabled = false

[mobile]
    enabled = false

[blocking]
    enabled = false

is that possible problem?

It didn't seem to be..

dot I disabled b/c I saw what looked like android devices auto discover the dot endpoint.. (need to test that more)

3 -
[Suggestion]
In the logs.. I cannot confirm that upstream and forwarding are going to different end points easily..

Possibly designate UPSTREAM (related to the [upstream] block) and FORWARD (related to the forwarding block)

4 -
Next block of spare time will be on zones.. possible wildcard support?

ie

time.onsite = A 10.20.30.40
pool.ntp.org = CNAME time.onsite
*.pool.ntp.org = CNAME time.onsite

(or someway to make that happen.. )

Thank you again for taking the time to read this.

(thank you for all your attention) 1 - [upstream] and address seems to work with multiple endpoints: numa.toml example file: ``` # [upstream] # mode = "forward" # "forward" (default) — relay to upstream # # "recursive" — resolve from root hints (no address needed) # address = "9.9.9.9" # single upstream (plain UDP) # address = ["192.168.1.1", "9.9.9.9:5353"] # multiple upstreams — SRTT picks fastest ``` also numa.toml example file: ``` # [[forwarding]] # DoT upstream: tls://IP[:port]#hostname # suffix = ["google.com", "goog"] # hostname is the TLS SNI / cert name # upstream = "tls://9.9.9.9#dns.quad9.net" # port 853 default ``` doing an: upstream = "tls://9.9.9.9:853#dns.quad9.net" , "tls://149.112.112.112:853#dns.quad9.net" or upstream = [ "tls://9.9.9.9:853#dns.quad9.net" , "tls://149.112.112.112:853#dns.quad9.net" ] (assuming that the bootstrap'ing is not the problem) 2 - (I also have these disabled while I'm working through the features and syntax) ``` [dot] enabled = false [proxy] enabled = false [mobile] enabled = false [blocking] enabled = false ``` is that possible problem? It didn't seem to be.. dot I disabled b/c I saw what looked like android devices auto discover the dot endpoint.. (need to test that more) 3 - [Suggestion] In the logs.. I cannot confirm that upstream and forwarding are going to different end points easily.. Possibly designate UPSTREAM (related to the [upstream] block) and FORWARD (related to the [[forwarding]] block) 4 - Next block of spare time will be on zones.. possible wildcard support? ie time.onsite = A 10.20.30.40 pool.ntp.org = CNAME time.onsite *.pool.ntp.org = CNAME time.onsite (or someway to make that happen.. ) Thank you again for taking the time to read this.

bcookatpcsd commented

2026-04-17 00:31:17 +08:00

(Migrated from github.com)

also looks better; clearer

<img width="913" height="170" alt="Image" src="https://github.com/user-attachments/assets/0609a4fd-cd50-4fd9-b9e3-8e537e9a4f17" /> also looks better; clearer

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/numa#102