* Tell dnsmasq not to pass requests upstream
The behavior of dnsmasq changed in version 2.86 -- before then, if a record was set for a domain name with dnsmasq, and a record for a type not specified for that domain was requested, dnsmasq would indicate no data existed for that record type. After 2.86, record types that are not specified are instead passed upstream. The latter behavior causes problems for, e.g., the Steam client, which will disregard a correctly set A-record for lancache.steamcontent.com, if no AAAA is set with dnsmasq and dnsmasq passes the AAAA query upstream. The documentation for dnsmasq indicates the correct way to restore the old behavior is to use the local=/host/ syntax -- emit this syntax for each of our lancache-hosted DNS entries.
* Update scripts/create-dnsmasq.sh
Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
---------
Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
This change addresses some general housecleaning for CDN hosts:
* Removing all hosts that do not resolve
* Only including the Steam CDN trigger address
This change addresses some general housecleaning for CDN hosts:
* Removing all hosts that do not resolve
* Removing any rogue whitespaces in CDN `.txt` files
* Removing hirez CDN (as the only host could not be resolved)
* add script to generate bind response policy zone for dns manipulation/filtering
* rpz: support custom basedomain via cli arg
* Update create-rpz.sh
* changed times to match current lanacache_dns
[Dnsmasq version >= 2.86](https://thekelleys.org.uk/dnsmasq/CHANGELOG) supports passing multiple IP addresses via the `address=` syntax now.
>Major rewrite of the DNS server and domain handling code. The change makes multiple addresses associated with a domain work address=/example.com/1.2.3.4 address=/example.com/5.6.7.8.
This allows us to simplify the script and the `.hosts` file workaround is no longer necessary.
#149 introduced a minor regression which included duplicates for the Unbound generation script.
While this does not have a technical impact it may cause confusion for users, this PR will ignore duplicate entries.
