PullFromGitHub/numa
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 25 Wiki Activity

forward rule stopped? #147

New Issue
Closed
opened 2026-04-24 22:14:01 +08:00 by dearsky · 1 comment
dearsky commented 2026-04-24 22:14:01 +08:00 (Migrated from gitea.proxy.dearsky.top)
Copy Link

I have numa setup via runit (like s6/daemontools but smaller/easier than s6) and wasn't logging..

it happened twice, but now I'm logging.. and this instance is somewhat busy..

Image
  • I had a forward for a domain tld and in-addr.arpa which seemed to stop working..

so (autodiscovery) of proxy.domain and forward for "domain" was working last night when I went home.. and by 7 am when the world showed up, proxy.domain was not resolving..

I checked the config and it was correct, but drill/kdig again the server did not return the records.. bounced the server and the drill/kdig worked.. (I assumed I left something off last night..)

then by 8:30 same issue.. so I just hardcded two zone entries for the auto discovery response, and left the forwarding in place..

Is now 10am ish and all seems fine.. but I have those hardcoded entries..

Just wanted to report in case I find something..

and it is on a higher concurrency qps in case that might ever be anything..

🤷

OT: Thank you as always for this crazy efficient piece of feature rich software..

I have numa setup via runit (like s6/daemontools but smaller/easier than s6) and wasn't logging.. it happened twice, but now I'm logging.. and this instance is somewhat busy.. <img width="922" height="193" alt="Image" src="https://github.com/user-attachments/assets/d1953fa7-1db1-44e3-a96f-0469970bf961" /> - I had a forward for a domain tld and in-addr.arpa which seemed to stop working.. so (autodiscovery) of proxy.domain and forward for "domain" was working last night when I went home.. and by 7 am when the world showed up, proxy.domain was not resolving.. I checked the config and it was correct, but drill/kdig again the server did not return the records.. bounced the server and the drill/kdig worked.. (I assumed I left something off last night..) then by 8:30 same issue.. so I just hardcded two zone entries for the auto discovery response, and left the forwarding in place.. Is now 10am ish and all seems fine.. but I have those hardcoded entries.. Just wanted to report in case I find something.. and it is on a higher concurrency qps in case that might ever be anything.. 🤷 OT: Thank you as always for this crazy efficient piece of feature rich software..
dearsky commented 2026-04-25 18:51:00 +08:00 (Migrated from gitea.proxy.dearsky.top)
Copy Link

@bcookatpcsd this is a real bug you found, again! Thank you! I created the above pr for it which should solve it. I would like to do more tests before merging

@bcookatpcsd this is a real bug you found, again! Thank you! I created the above pr for it which should solve it. I would like to do more tests before merging
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 docker
Pull requests that update docker code
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 rust
Pull requests that update rust code
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: PullFromGitHub/numa#147
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?