Expected Behaviour:
I am installing PiHole in a VM running Arch Linux with the AUR packages pi-hole-server. I followed the instructions on the Arch Wiki including modifying PHP and lighttpd. The only thing I am doing differently is that during installation, I manually edit /etc/pihole/setupVars.conf to
$ cat /etc/pihole/setupVars.conf
INSTALL_WEB_INTERFACE=true
QUERY_LOGGING=true
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=false
DNSSEC=false
PIHOLE_INTERFACE=enp1s0
IPV4_ADDRESS=
IPV6_ADDRESS=
DNSMASQ_LISTENING=local
BLOCKING_ENABLED=true
REV_SERVER=true
REV_SERVER_CIDR=192.168.16.0/24
REV_SERVER_TARGET=192.168.16.2
REV_SERVER_DOMAIN=lan
WEBPASSWORD=<PASSWORD>
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
The PiHole machine is given an IP address of 192.168.16.3 from my local DHCP/DNS server which is running at 192.168.16.2. I expect that when I reboot, that PiHole will forward *.lan addresses to be resolved by 192.168.16.2.
Actual Behaviour:
Although I have not really tested it, upon reboot PiHole seems to start up correctly and function properly except for forwarding *.lan address. If I navigate to http://192.168.16.3/admin/settings.php?tab=dns and click on save without changing anything and reboot, the forwarding *.lan address works.
Is there a way to manually refresh whatever needs to be refreshed from the CLI?
Debug Token:
# pihole -d
Pi-hole debug options are disabled.
ArchLinux distribution of Pi-hole is not supported by official project and this debug report CAN NOT be uploaded to their debug team.
Follow instructions carefully on the project wiki page (https://wiki.archlinux.org/index.php/Pi-hole) and please refer to AUR package web page for support and debugging (https://aur.archlinux.org/packages/pi-hole-server).