nsone -- list index out of range. about lexicon HOT 6 CLOSED

Adding more info.

Dumping the record information before processing reveals that the problem is with nsone "linked" records.

...
{u'domain': u'sitelabs.io', u'short_answers': [u'dns1.p03.nsone.net', u'dns2.p03.nsone.net', u'dns3.p03.nsone.net', u'dns4.p03.nsone.net'], u'ttl': 3600, u'tier': 1, u'type': u'NS', u'id': u'599ce1d3a632f60001a95c76'}
{u'domain': u'sitelabs.io', u'short_answers': [u'v=spf1 mx -all'], u'link': None, u'ttl': 3600, u'tier': 1, u'type': u'TXT', u'id': u'59a479fda632f6000199e90b'}
{u'domain': u'www.sitelabs.io', u'short_answers': [], u'link': u'sitelabs.ca', u'ttl': 3600, u'tier': 1.0, u'type': u'A', u'id': u'59ac55a1a632f60001df4361'}
...

In this case. www.sitelabs.io is linked to sitelabs.ca

I'll let you decide whether you should recurse (and fetch the linked record), just fake a CNAME, or just skip, but that's a corner case that needs special treatment in any case.

from lexicon.

Hmm, I'm not really familiar with NSOne's link feature. Is this something you can open a PR to fix?

from lexicon.

It's a way for nsone users to de-duplicate dns record information, without requiring dns clients to pay the price of a CNAME. It effectively makes a record a symbolic link to another one on their database.

https://ns1.com/articles/cname-alias-and-linked-records

I'm happy to patch it, but should the "linked" status be exposed in the lexicon output? Fetching details for a linked record would require another dnsone API lookup. Is there another provider which has a similar feature, and from which the behaviour could be replicated?

from lexicon.

Looking at what you said, I think it would make sense to fake a CNAME record for it, with another API lookup.

I don't think there's an example of another provider doing anything similar, unfortunately.

from lexicon.

Created PR #157 .

from lexicon.

This should be fixed now thanks to @init-js . Closing.

from lexicon.