-
-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using linked zones with nsone won't resolve to the main zone #1990
Comments
I would be glad to review a PR for this issue ! |
It seems like the changes in #151 were just to add the possibility to list records and that didn't work for me. I think it was due to a comparison to None instead of comparing to an empty string for the link. With these changes to nsone.py, it works for me and it will also resolve linked zones (no recursion is possible when it comes to linked zones):
The feature request was about was to be able to add records to these linked zones, and that will need more work. |
Alright, I did an easy method to get to the linked zone. I'm not sure if this is the way it's normally done in the rest of the code, but it seems to work as intended for me. |
Using NS1, if there's two domains example1.tld and example2.tld, where example2.tld is a linked zone to example1.tld, Lexicon won't follow this link and fails with this error:
I noticed that linked records were fixed in issue #151, and I'd guess some similar approach would work with linked zones.
Using the NS1 API, it's possible to do a zone info request, View zone details and the linked zone is returned as the "link" property.
The text was updated successfully, but these errors were encountered: