mirror of
https://github.com/lancachenet/monolithic
synced 2024-11-22 03:53:06 +00:00
Update faq.md with Goten's mini howto for systemd-resolved
@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:
parent
eb434e9d56
commit
319abc80e1
1 changed files with 9 additions and 0 deletions
9
faq.md
9
faq.md
|
@ -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?
|
## 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
|
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`)
|
||||||
|
|
Loading…
Reference in a new issue