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.

Sign up for GitHub

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

Jump to bottom

Support DNS over TCP/IP transport and retry truncated UDP responses #19

Closed
clue opened this issue Feb 23, 2015 · 5 comments · Fixed by #148
Closed

Support DNS over TCP/IP transport and retry truncated UDP responses #19

clue opened this issue Feb 23, 2015 · 5 comments · Fixed by #148
Assignees
@clue
Labels
new feature
Milestone
v1.2.0

Comments

@clue
Copy link
Member

clue commented Feb 23, 2015

Resolution via TCP transport should use the react/socket-client component.

Fixes #11 and #13.
@clue
Copy link
Member Author

clue commented Feb 23, 2015

Depends on reactphp-legacy/socket-client#12 so that the socket-client component does not depend on a DNS Resolver instance again.

@clue clue mentioned this issue Feb 23, 2015
Closed
@clue clue mentioned this issue Sep 3, 2015
Closed
@clue clue modified the milestone: v0.5 Feb 24, 2016
@clue clue added the bug label Nov 16, 2016
@clue clue mentioned this issue Feb 12, 2017
Merged
@clue clue self-assigned this Feb 12, 2017
This was referenced Feb 13, 2017
Merged
Merged
Merged
@clue clue modified the milestones: v0.5, v0.4.6 Feb 13, 2017
@clue clue modified the milestones: v0.4.7, v0.4.6 Mar 10, 2017
@clue clue mentioned this issue Mar 30, 2017
Merged
@clue clue modified the milestones: v0.4.8, v0.4.7 Mar 30, 2017
@clue clue changed the title Should use socket-client component Should use Socket component for TCP/IP connections Apr 10, 2017
@clue
Copy link
Member Author

clue commented Apr 10, 2017

Updated title now that the SocketClient component has been deprecated via reactphp/socket#74

@jsor jsor modified the milestones: v0.4.9, v0.4.8 Apr 16, 2017
@clue clue modified the milestones: v0.4.10, v0.4.9 May 1, 2017
@clue clue modified the milestones: v0.5.0, v0.4.10 Aug 9, 2017
@clue clue changed the title Should use Socket component for TCP/IP connections Support TCP/IP queries and retry fragmented via Socket component Aug 9, 2017
@clue clue removed the bug label Aug 9, 2017
@clue clue mentioned this issue Aug 9, 2017
Merged
@clue clue mentioned this issue Sep 11, 2017
Closed
@clue
Copy link
Member Author

clue commented Sep 12, 2017

This ticket is ready to be implemented in a future version 👍

For the reference: See also the updated RFC 7766 and the old RFC 1035

This was referenced Sep 12, 2017
Open
Closed
@cboden cboden mentioned this issue Sep 12, 2017
Closed
@clue clue mentioned this issue Feb 5, 2018
Closed
@clue clue mentioned this issue Feb 27, 2018
Merged
@someniatko
Copy link

@clue Any estimates, please?

@clue
Copy link
Member Author

clue commented Mar 23, 2018

As much as I'd like to commit to specific date, I can only say that we will get to this feature as soon as time permits.

If you want to sponsor this feature, feel free to reach out 👍

@clue clue mentioned this issue Jun 25, 2018
Merged
@clue clue changed the title Support TCP/IP queries and retry fragmented via Socket component Support DNS over TCP/IP transport and retry truncated UDP responses Jun 29, 2018
@clue clue removed this from the v0.5.0 milestone Jul 3, 2019
This was referenced Jul 10, 2019
Closed
Merged
This was referenced Aug 2, 2019
Merged
Merged
@clue clue added this to the v1.2.0 milestone Aug 9, 2019
This was referenced Aug 9, 2019
Merged
Merged
@jsor jsor closed this as completed in #148 Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@clue clue

Labels
new feature
Projects
None yet
Milestone
v1.2.0
3 participants
@jsor @clue @someniatko