Mirrors/monolithic
2
0
Fork 0
mirror of https://github.com/lancachenet/monolithic synced 2024-11-22 03:53:06 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update faq.md with Goten's mini howto for systemd-resolved

Browse source 
@GotenXiao I nabbed this from the discussion the other day.  It feels worthy of being in the FAQ for mono?
This commit is contained in:
Barry Zubel 2020-02-12 19:06:40 +00:00 committed by GitHub
parent eb434e9d56
commit 319abc80e1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
faq.md
View file

@ -77,3 +77,12 @@ Other options also involve transparently intercepting HTTP traffic at a network
## Can I load some content into the cache ahead of my event?
You could look at [zeropingheroes/lancache-autofill](https://github.com/zeropingheroes/lancache-autofill) as an aide to pre-loading popular games into the cache ahead of time to help kick start the cache
### Disabling `systemd-resolved` DNSStubListener
If your cache host is running a recent Linux distribution, it is likely running `systemd-resolved`, which listens on port `53`. If you want your cache host to bind to `0.0.0.0:53` (INADDR_ANY, all IPv4 addresses), you will first need to disable `systemd-resolved`'s stub listener.
1. Run `sudo -e /etc/systemd/resolved.conf` and change the line starting with `#DNSStubListener=` to `DNSStubListener=no` - _removing the `#` is important_
1. Run `sudo rm /etc/resolv.conf`
1. Run `sudo ln -s /var/run/systemd/resolve/resolv.conf /etc/resolv.conf`
1. Run `sudo service systemd-resolved restart`
1. Check that you can still resolve DNS on the cache server by running `nslookup` for a domain of your choice (e.g. `lancache.net`)