in-addr.arpa aggressive? confused? #94

New Issue

2026-04-13T10:28:43+08:00

bcookatpcsd commented

2026-04-13 10:28:43 +08:00

(Migrated from github.com)

I thought it was because I missed the double brackets..

[[forwarding]]
	#suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"]
	suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite"]
	upstream = "192.168.88.1:53"

defining the 188 in-addr.arpa and 88 in-addr.arpa going to the same upstream does not seem to work..

but the entire 168.192 in-addr.arpa also does not

(to be clear)

[[forwarding]]
	# none of these in-addr.arpa work
        # suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"]
	# suffix = [ "188.168.192.in-addr.arpa", "188.onsite", "onsite"]
        # but this does not either
        suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite" ]
	upstream = "192.168.88.1:53"

 drill -Q -x 192.168.188.153 @192.168.88.1
omarchy-445.188.onsite.
 drill -Q -x 192.168.188.153 @192.168.188.252
(nothing

also doing 168.192.in-addr.arpa all by it self does not either..

[[forwarding]]
	suffix = [ "168.192.in-addr.arpa" ]
	upstream = "192.168.88.1:53"

2026-04-13_02:21:22.64466 [2026-04-13T02:21:22.644Z INFO numa::ctx] 192.168.188.153:50392 | PTR 153.188.168.192.in-addr.arpa | LOCAL | NXDOMAIN | 0ms

(I have many /20's - almost all 16 that I'm liking to try this on.. if that helps for scope.. )

Thank you in advance for your time.

I thought it was because I missed the double brackets.. ``` [[forwarding]] #suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"] suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite"] upstream = "192.168.88.1:53" ``` defining the 188 in-addr.arpa and 88 in-addr.arpa going to the same upstream does not seem to work.. but the entire 168.192 in-addr.arpa also does not (to be clear) ``` [[forwarding]] # none of these in-addr.arpa work # suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"] # suffix = [ "188.168.192.in-addr.arpa", "188.onsite", "onsite"] # but this does not either suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite" ] upstream = "192.168.88.1:53" ``` ``` drill -Q -x 192.168.188.153 @192.168.88.1 omarchy-445.188.onsite. drill -Q -x 192.168.188.153 @192.168.188.252 (nothing ``` also doing 168.192.in-addr.arpa all by it self does not either.. ``` [[forwarding]] suffix = [ "168.192.in-addr.arpa" ] upstream = "192.168.88.1:53" ``` 2026-04-13_02:21:22.64466 [2026-04-13T02:21:22.644Z INFO numa::ctx] 192.168.188.153:50392 | PTR 153.188.168.192.in-addr.arpa | LOCAL | NXDOMAIN | 0ms (I have many /20's - almost all 16 that I'm liking to try this on.. if that helps for scope.. ) Thank you in advance for your time.

razvandimescu commented

2026-04-13 15:01:28 +08:00

(Migrated from github.com)

ah @bcookatpcsd sorry for that i tested in isolation not the whole pipeline and special-use domain intercept was running before forwarding rules, so *.168.192.in-addr.arpa always returned local NXDOMAIN regardless of your forwarding config.
Fixed in #95 - forwarding rules now take precedence.
Until we have a new release you could try it now with:

git clone https://github.com/razvandimescu/numa && cd numa
cargo build --release
sudo ./target/release/numa install

ah @bcookatpcsd sorry for that i tested in isolation not the whole pipeline and special-use domain intercept was running before forwarding rules, so *.168.192.in-addr.arpa always returned local NXDOMAIN regardless of your [[forwarding]] config. Fixed in #95 - forwarding rules now take precedence. Until we have a new release you could try it now with: ``` git clone https://github.com/razvandimescu/numa && cd numa cargo build --release sudo ./target/release/numa install ```

👍 1

bcookatpcsd commented

2026-04-13 18:54:35 +08:00

(Migrated from github.com)

Confirmed working..

will further test different variants

tail -F /tmp/numa/current | grep 'onsite\|in-addr.arpa'

2026-04-13_10:46:55.45496 [2026-04-13T10:46:55.454Z INFO  numa::ctx] 192.168.188.153:59737 | PTR 153.188.168.192.in-addr.arpa | FORWARD | NOERROR | 1ms
2026-04-13_10:47:07.27487 [2026-04-13T10:47:07.274Z INFO  numa::ctx] 192.168.188.153:46599 | PTR 153.188.168.192.in-addr.arpa | CACHED | NOERROR | 0ms

and

drill -Q -x 192.168.188.153 @192.168.188.252
omarchy-445.188.onsite.

current config section:

[[forwarding]]
	# suffix = [ "188.168.192.in-addr.arpa" ]
	upstream = "192.168.88.1:53"
	suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"]
	# suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite"]

will test more today.

Greatly appreciate the effort.

Confirmed working.. will further test different variants ``` tail -F /tmp/numa/current | grep 'onsite\|in-addr.arpa' 2026-04-13_10:46:55.45496 [2026-04-13T10:46:55.454Z INFO numa::ctx] 192.168.188.153:59737 | PTR 153.188.168.192.in-addr.arpa | FORWARD | NOERROR | 1ms 2026-04-13_10:47:07.27487 [2026-04-13T10:47:07.274Z INFO numa::ctx] 192.168.188.153:46599 | PTR 153.188.168.192.in-addr.arpa | CACHED | NOERROR | 0ms ``` and ``` drill -Q -x 192.168.188.153 @192.168.188.252 omarchy-445.188.onsite. ``` current config section: ``` [[forwarding]] # suffix = [ "188.168.192.in-addr.arpa" ] upstream = "192.168.88.1:53" suffix = [ "188.168.192.in-addr.arpa", "88.168.192.in-addr.arpa", "188.onsite", "onsite"] # suffix = [ "168.192.in-addr.arpa", "188.onsite", "onsite"] ``` will test more today. Greatly appreciate the effort.

🎉 1

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/numa#94