martydingo

Right, it's not erroring but I'm not seeing the circuit between a patch panel and a router, so it goes from router -> 24 LC patch panel (unnamed) then to...

Well people should be putting things like circuits into patch panels as standard, unless it's just the one circuit being used as a WAN, that I can understand. Thanks very...

Is there any progress on this?

Actually, looking through Netbox itself, it's a dropdown of nameservers, not an integer as described in the image below. 

Thanks very much for going into so much detail into this issue. It's an odd one, with the API reporting this as an integer. Netbox API is running `3.1` according...

That nameserver is also already configured on Netbox ```json { "count": 2, "next": null, "previous": null, "results": [ { "id": 1, "url": "http://10.84.0.2/api/plugins/netbox-dns/nameservers/1/", "display": "a.dns.dingo.management", "name": "a.dns.dingo.management", "tags": [], "created":...

With these assortment of small differences (default_ttl being required, soa_mname reporting as an integer) I believe there's going to be an issue with my environment, it's the only thing I...

Oh yeah this is definitely most likely a layer 8 problem with myself. I added a json.dumps to the API call, and then I see ```json { "name": "home.dingo.services", "default_ttl":...

Interesting, I had put this on hold as time is not-so-spare. Happy to test any fixes.

Okay cool, will do and will update.