If hostname is an empty string then the current Sends hostname to the DHCP server so it can be registered lighttpd has an additional nf file with "server.port = 8080". I understand this is something to do with 'loopback' Interestingly running the inbuilt generate debug log also fires up dhcp-discover and generates the same error Įverything appears to be working so do I just ignore the lo warning, or does it suggest something in my setup needs attention? "Warning in dnsmasq core: no address range available for DHCP request via lo" However, if I then run pihole-FTL dhcp-discover I get a new warning. This has been done and the problems described appear to have gone away. "# Inform the DHCP server of our hostname for DDNS. I subsequently discovered that I had foolishly not amended the dhcpdc file to reflect the hostname under I followed your wise guidance and rebooted. Thank you for taking the time to respond. …and then the “.unable to resolve host….” warning returns.Ĭan any kind soul please give me a shove in the right direction? "127.0.0.1 pihole-server" from the Hosts file Not giving name pihole-server to the DHCP lease of 192.168.1.251 because the name exists in /etc/hosts with address 127.0.0.1" Not giving name pihole-server.lan to the DHCP lease of 192.168.1.251 because the name exists in /etc/hosts with address 127.0.0.1 This nag goes away and I get another warning “sudo: unable to resolve host pihole-server: Name or service not known” When updating Pi or restarting services I get
SUDO UNABLE TO RESOLVE HOST BPC HOW TO
I am stuck in a circle and have no idea how to escape.
0 kommentar(er)
