Skip to content
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

Support SOA records ($50) #37

Closed
campadrenalin opened this issue Jul 24, 2013 · 4 comments
Closed

Support SOA records ($50) #37

campadrenalin opened this issue Jul 24, 2013 · 4 comments

Comments

@campadrenalin
Copy link
Owner

http://docstore.mik.ua/orelly/networking_2ndEd/dns/appa_01.htm#INDEX-2486

SOA records seem to be the final stumbling block on the way to being able to correctly resolve ICANN AAAA records, like urlcloud.net. This ticket involves adding support in record.py for SOA binary packing and unpacking according to the spec (see link above).

Probably, the best intermediate form for rdata would be a namedtuple.

@campadrenalin
Copy link
Owner Author

Bounty is $50.

http://www.freedomsponsors.org/core/issue/305/support-soa-records


(Copied from acceptance criteria)

Add distinctly recognized record type, and appropriate pack and unpack functions, to record.py. Store the data as a namedtuple.

@pczarn
Copy link
Contributor

pczarn commented Aug 14, 2013

Could the data be stored as a dict? Perhaps either should be acceptable?

There are no namedtuples in JSON, so json.py would need to recognize record types.

@campadrenalin
Copy link
Owner Author

Oh, good point. I totally forgot about the need for JSON serialization
support. Yeah, dict is good.

On Wed, Aug 14, 2013 at 3:01 PM, Piotr notifications@github.com wrote:

Could the data be stored as a dict? Perhaps either should be acceptable?

There are no namedtuples in JSON, so json.py would need to recognize
record types.


Reply to this email directly or view it on GitHubhttps://github.com//issues/37#issuecomment-22670718
.

@campadrenalin
Copy link
Owner Author

Excellent work, again, @pczarn. All I had to do is fix a simple merge conflict caused by merging the other branch earlier. Be sure to mark these as complete on Freedomsponsors so I can pay you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants