max-mapper / max-mapper/HyperOS
have hypercore inherit host OS DNS
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 124
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
today on a university network that blocked ports etc, I ran into an issue where having /etc/resolv.conf configured with nameserver 192.168.64.1 worked, but nameserver 8.8.8.8 (google DNS) did not work
on other networks i've experienced the opposite being true -- google DNS fixes dns resolution, but using 192.168.64.1 didn't work
It would be nice to solve this for 100% of cases. I'm not an expert in this area, suggestions appreciated
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
Start by investigating how HyperOS and hypercore currently obtain or configure DNS, using the reported /etc/resolv.conf values as the reproduction case. Compare host OS DNS behavior with 192.168.64.1 and 8.8.8.8; done means DNS resolution works across the network conditions described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100