Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
NS1 Provider: Dynamic Records - NotifyList too many characters
See original GitHub issueI have run into an issue while testing out dynamic records using the NS1 provider that manifests itself with the following error.
"ns1.rest.errors.ResourceException: server error: Input validation failed (Value u'dynamic-routing-record.poc-test-octo.example.com - A - 10.10.10.10' for field '<obj>.name' must have length less than or equal to 64)"
The error appears to be a limitation of the NS1 API not accepting strings longer than 64 characters for their healthchecks / monitors. The way that octodns assembles the string used for the name of the healthcheck, more times than not, I’d run into this issue with the majority of my dynamic services.
When I reduce the number of characters in either the name of the dynamic record itself or the target values in the dynamic pools, I can get past this issue, but this is not ideal or always possible.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I was able to confirm this error when manually hitting the notification list api! I have contacted NS1 and provided them my findings too! Hopefully they can increase the allowed characters limit. If not, perhaps some of the hashing logic previously mentioned might be needed?
Found a general issue with NS1 record cleanup while digging into things related to this issue https://github.com/octodns/octodns/pull/748