summaryrefslogtreecommitdiff
path: root/Base/etc/LookupServer.ini
AgeCommit message (Collapse)Author
2021-02-15LookupServer: Implement a DNS server :^)Sergey Bugaev
LookupServer can now itself server as a DNS server! To service DNS clients, it uses the exact same lookup logic as it does for LibIPC clients. Namely, it will synthesize records for data from /etc/hosts on its own (you can use this to configure host names for your domain!), and forward other questions to configured upstream DNS servers. On top of that, it implements its own caching, so once a DNS resource record has been obtained from an upstream server, LookupServer will cache it locally for faster future lookups. The DNS server part of LookupServer is disabled by default, because it requires you to run it as root (for it to bind to the port 53) and on boot, and we don't want either by default. If you want to try it, modify SystemServer.ini like so: [LookupServer] Socket=/tmp/portal/lookup SocketPermissions=666 Priority=low KeepAlive=1 User=root BootModes=text,graphical and enable server mode in LookupServer.ini like so: [DNS] Nameservers=... EnableServer=1 If in the future we implement socket takeover for IP sockets, these limitations may be lifted.
2020-10-25LookupServer: Support multiple nameserversLinus Groh
The configuration key [DNS] Nameserver has been renamed to Nameservers and accepts a comma-separated list of nameserver addresses, which will be queried in the given order until a response has been received. The new default value is still Cloudflare's 1.1.1.1 as well as their secondary DNS server 1.0.0.1.
2020-01-26LookupServer: Rename setting "DNS/IPAddress" => "DNS/Nameserver"Andreas Kling
2019-12-11LookupServer: Switch to a more privacy-respecting DNS providerValtteri Koskivuori
2019-06-07LookupServer: Load hostnamesChristopher Dumas
2019-05-27Network stack is now configurable, and resolution is also configurable, but ↵Christopher Dumas
loading cursors causes a page-fault?