-
Notifications
You must be signed in to change notification settings - Fork 19
Conversation
I rolled this version out in my own production environment today and was able to correctly import all my DNS data as they currently are in my DNS infrastructure, views and all. After some minor issues it now works smoothly for me, so I guess this PR is ready for review. |
I'm working with this in my home setup and am having some problems with the REST API. The normal web interface works OK. So far the problems I'm seeing are:
|
Hi @jcollie, thanks! Would you mind opening a separate issue for each of the problems? I'll look into them as soon as possible. If possible, please also include the request that led to the issue. That makes reproducing and testing easier. |
I figured out the record creation issue, I had to specify |
Opened issue #171 |
Querying by view name still doesn't work. Querying by view ID works now that I tried setting up a small reproducer. |
The latest version should take care of the issues. Thanks again @jcollie for reporting! |
Things are looking good with the latest patches. I've even ginned up a octodns-netbox-dns module that hooks octoDNS into NetBox DNS. Note that there's a bug in pynetbox that will cause problems. Fortunately there's a pull request to fix it, unfortunately it's been sitting there for a while without any action. |
…or message in the GUI
Just rebased to the current main. Currently I don't have anything on my list that needs attention, so unless someone else finds something missing/going wrong I'm not planning any further changes to this PR. |
fixes #15
fixes #171
fixes #173
This PR adds the long awaited feature of "Views" to NetBox DNS.
A view essentially is only an optional name that can be added to any zone. There are two consequences if a zone is associated with a view:
There is some rather involved logic in place that kicks in when zones are moved from one view to the other or when zones are added or removed from views. Generally the code tries to do "the right thing", i.e. doesn't create duplicate zones in the same or without a view and move the PTR records between reverse zones when the zone containing the address records is moved.