netstack issueshttps://gitlab.redox-os.org/redox-os/netstack/-/issues2018-06-13T18:35:09Zhttps://gitlab.redox-os.org/redox-os/netstack/-/issues/7Implement netcfg2018-06-13T18:35:09ZDan RobertsonImplement netcfgImplement _netcfg_ as described in redox-os/rfcs#6Implement _netcfg_ as described in redox-os/rfcs#6https://gitlab.redox-os.org/redox-os/netstack/-/issues/9Implement dnsd2018-06-13T18:35:09ZJeremy SollerImplement dnsd*Created by: batonius*
Currently, there's no centralized DNS subsystem in Redox and two independent implementations of `lookup_host` in `stdlib` and `newlib`. By implementing a specialized daemon we'll be able to cache DNS requests, per...*Created by: batonius*
Currently, there's no centralized DNS subsystem in Redox and two independent implementations of `lookup_host` in `stdlib` and `newlib`. By implementing a specialized daemon we'll be able to cache DNS requests, perform reverse queries, and provide clear, user-friendly interface to DNS queries.
The new daemon should implement `dns:` schema, so a process could open `dns:example.org` and read resolved IPv4 (for now) in string format. Other record types could be implemented in the future as "dns:aaaa/example.org". The daemon should keep resolved domains in a cache for a configurable amount of time.
Once #7 is implemented, the daemon should get the addrs of the DNS server from `netcfg:resolv/server`.