How "/etc/resolv.conf" is configured?
- Dominant language
- C
- Stars
- 20.5k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
Dear experts,
it is quite annoying that my **/etc/resolv.conf** (iPad with ish downloaded from the official app store) looks like this:
```
search local
nameserver 198.18.0.1
```
Addresses from the range 198.* are used nowhere in my local network. The DNS is done by an OPNsense device being served by two different Pi-hole servers (more or less as described [here](https://pi-hole.net/blog/2021/09/30/pi-hole-and-opnsense/)). It is a dual stack IPv4/IPv6 environment and I'd very much like to be able to define the correct DNS server somewhere in the ish preferences as "198.18.0.1" doesn't even know my local network devices for whatever reason. Changing **/etc/resolv.conf** doesn't work as it is overwritten when restarting ish.
I'm currently confined to bed so any solution (couldn't live without ish as it gives freedom) would be profoundly appreciated!
Further questions are happily answered!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining how /etc/resolv.conf is generated and overwritten when iSH restarts, and where iSH preferences are defined; the issue names no source file or test. Reproduce the reported 198.18.0.1 configuration on iPad and determine whether DNS can be configured persistently. Done means the supported DNS behavior is implemented or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, linux
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100