Support DNS UPDATE messages (client and server) in Twisted Names
Open
Nobody has claimed this yet.
enhancement
names
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@exarkun reported |
|---|---|
| Trac ID | trac#2499 |
| Type | enhancement |
| Created | 2007-03-01 16:06:12Z |
Jeff Silver worked up a patch for this a while ago. Alas, it doesn't include unit tests, and only attempts to deal with the server side of this, but it may at least provide a starting point for something else.
http://twistedmatrix.com/pipermail/twisted-python/2005-February/009644.html
Searchable metadata
trac-id__2499 2499
type__enhancement enhancement
reporter__exarkun exarkun
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__names names
keywords__
time__1172765172000000 1172765172000000
changetime__1436309785183543 1436309785183543
version__None None
owner__
cc__rainhead cc__clokep
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named in the issue. Start by reviewing Twisted Names' existing DNS client and server handling and the linked historical patch; the work is done when DNS UPDATE messages are supported on both sides and unit tests cover the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100