-
-
Notifications
You must be signed in to change notification settings - Fork 61
[WIP] DNS Server Implementation #9
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
Conversation
- Added debugging methods (dig like output) and HumanParser - Added support for MX, NS, TXT, PTR, SOA records - Added example scripts
parser to not chock on types not implemented yet
- Added transport info at Message level to parse/binarydump TCP/UDP properly. In TCP first two octets describes the length of data -- Added execution time calculation to Message and pretty EXPLAIN() with nameserver and data size info - Added CODE type to Record for Humans - Added binarydumper for Answers, Authority & Additional (this now covers RobinvdVleuten'shttps://github.com/reactphp/reactphp/pull/272)
|
@igorw This is pending test cases, but I am putting it up for your review of nameserver implementation. Your feedback is appreciated. Thanks |
…TYPE and added some test cases around that
…e to either Human or Machine code
|
@clue server implementation is piggy backing on #8; otherwise the server implementation itself is pretty small. You can see additional server setup examples I have drafted without the clutter @ https://github.com/hathoora/babaji-dns/tree/master/experiment |
(Missing test cases for Server, but would like the implementation to be reviewed)
Current Server implementation: