Dynamic Configuration Of Bind Configurations Via Rocket API #8
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
help wanted
invalid
maintenance
peach-lib
peach-network
peach-oled
peach-stats
peach-web
question
refactor
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: PeachCloud/peach-dyndns-server#8
Loading…
Reference in New Issue
No description provided.
Delete Branch "talk-to-bind"
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?
The approach I've opted for is assuming a bind9 server is running, and creating a rocket server which adds configurations to bind to register new domains. Each new domain gets its own unique TSIG key, so that in the future the client can update the IP address for that domain using nsupdate and the TSIG key (and won't be able to update any other domains). This takes advantage of the authentication already built into bind and the DNS specs, without have to re-implement it.
The two rocket endpoints are:
I've tested that these endpoints are working on the server.
My next todos:
@mycognosist I'm merging this is now but would be happy to hear feedback whenever you have time. A bunch of rust in here, becoming less slow to write :)
btw the folders
/ns_tests
/bash
/bind_config
were more stuff I was using for debugging and I see I should actually clean up and remove those folders from git