mandatoryprogrammer / mandatoryprogrammer/TrustTrees
Issue when Following CNAME's
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 406
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Hey All,
There is an issue with TrustTrees when following a CNAME which results in false `REFUSED` responses being returned.
Currently when TrustTrees encounts a CNAME it will follow the CNAME and Query the CNAME's nameservers with the original domain instead of the CNAME Hostname.
Does this make sense? - I can provide an example domain it's happening with over Twitter @m0chan98
Cheers
~ @m0chan
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name files or tests. Start by locating TrustTrees' CNAME-following and nameserver-query entry points, then trace which hostname is passed after a CNAME is encountered. Reproduce the false REFUSED response with a CNAME example and verify that queries use the CNAME hostname rather than the original domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100