|
|
|
|
|
|
by cat199
1950 days ago
|
|
|
related question - anyone have any nice view-aware ways to deal with zone data? (and ideally, have some API and manage DHCP as well?) hacking together some scripts to export from a database, but would be nicer to use someone elses already-maintained hacked up scripts :) |
|
|
https://github.com/imoverclocked/xmdns
Basically, you:
1) setup a list of views (named.views) and edit the acls to match views based on how your dns servers will see your clients (named.acls) 2) setup a list of ip networks that you are going to resolve (res/db/net_list.xml) 3) modify you hosts with potentially single or multiple networks as necessary (res/db/host_list.xml)
There are some helper scripts in the root of the repo that bring you through the workflow of updating host_list.xml and generating your views.
Some nice things about this: you can set a per-network preference for what networks you try to connect to a host first if the host is multi-homed. This is useful for hopping over local links first and then traversing external hops if necessary.
When I ran it (7 years ago), the model was starting to slow down with several thousand nodes and ~30 networks because I just use xsltproc (command line tool) instead of writing something a little more streamlined.