Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/braheezy/go-dns-resolver
https://github.com/braheezy/go-dns-resolver
Last synced: 2 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/braheezy/go-dns-resolver
- Owner: braheezy
- Created: 2023-06-03T16:07:57.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-06-03T16:07:59.000Z (over 1 year ago)
- Last Synced: 2024-11-10T13:35:37.423Z (2 months ago)
- Language: Go
- Size: 2.93 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Go DNS Resolver (in a weekend)
This is a failed attempt at following this blog post: https://implement-dns.wizardzines.com/book/intro.html
They have a pretty nice guide on implementing a DNS resolver from scratch. They did it in Python and I tried to do it in Go. I spent several hours with ChatGPT trying to understand and fix the issues and never got it :(
## The Failure
After sending a DNS request to Google's nameservers and getting a response, the task is to parse the response into something meaningful. This program fails to parse Records that should be in the response after the Header and Questions, both things that are correctly parsed.
In the blog post guide I was following, they use a Python BytesIO buffer reader to operate on the response data. This is convenient because the pointer in the buffer is advanced as data is read, so functions can be chained together and benefit from pointer movement the previous function did.
This [confounding snippet](https://implement-dns.wizardzines.com/book/part_2.html#finish-our-dnsrecord-parsing) was shown:
In
```python
reader = BytesIO(response)
parse_header(reader)
parse_question(reader)
parse_record(reader)
```
Out:
```console
DNSRecord(name=b'www.example.com', type_=1, class_=1, ttl=21147, data=b']\xb8\xd8"')
```
The issue is that `parse_question` and `parse_record` both call `decode_name`, which would have advanced the buffer pointer past the name bytes in the response. So by the time `parse_record` is called, the pointer has moved too far and parsing starts to fail and get garbage data into the DNSRecord struct.
I was excited for the blog post but disappointed by the lack of explanation of the code. This disappointment was compounded by the fact that ChatGPT was unable to fix this rather simple program after quite a bit of back and forth. Womp womp.