Before I go any further, here's the debug token: zffjduce4b
These are two somewhat related issues in my opinion.I'm quite a newbie at this so please bear with me.
I went to the Settings tab in the Admin and then scrolled to DHCP leases. I wanted to add one permanent lease for my desktop PC, but after inputting the MAC address, IP and hostname (all correct) the settings would not take. I would not even update the page with the info I was putting in. I tried several variations and it did not work. I even tried assigning it with "dhcp-host=", but nothing. This is strange because I was able to do this a while back when I first installed pi-hole on my pi..
DHCP works for my phones and laptop, but my windows PC will just not get the correct IP and dns and even gateway. I have no Idea why. DHCP is handled by pi-hole. Here is what it gets: http://imgur.com/OMn2aUT . My local IPs are in this format however: 192.168.100.0/24
Is there an error message? What happens hen you click on Save (else than "nothing")? Please check in the Developer Tools (F12) if there is an error shown to you in case nothing happens at all.
The IP space 169.254.0.1/16 belongs to APIPA (Automatic Private IP Adressing). Win uses it when no DHCP server has been found on the network. Is the device correctly wired up? (as the other devices are working)
Is there an error message? What happens hen you click on Save (else than "nothing")? Please check in the Developer Tools (F12) if there is an error shown to you in case nothing happens at all.
It updates/refreshes the page and it does not update the fields. I don't recall seeing any message, error or otherwise.
The IP space 169.254.0.1/16 belongs to APIPA (Automatic Private IP Adressing). Win uses it when no DHCP server has been found on the network. Is the device correctly wired up? (as the other devices are working)
If I set up the manual IP and dns I get it working. Also it was working before using the router's DHCP, so I'm pretty sure it's not configured wrong. The only thing I can think about is that it has the static IP 192.168.100.2 assigned manually though the router interface, so I'm gonna remove that and try again just in case.
So basically it tells me it cannot reach the dhcp server, but we knew that already. I've also disabled the antivirus solution while running this. Any other ideas?
Later edit:
Did a pihole -r, set everything up again this time disabling ipv6 just as a shot in the dark (was causing issues on the Pi with apt-get). Now I managed to add the MAC and IP + hostnames, but the dhcp server is still not doing its job. I got an email that my evohome thermostat is down as well and upon trying to connect it I get an error as well. It seems that dhcp does not work at all.
Any ideas? New token is fie9ydlpi5. I have no idea how this worked for one day and then decided to stop. Also, I have pivpn installed and properly configured. Forgot to mention that.
As you have noted that other devices can get an IP from pihole's dhcp server, we know that it's working, and there's no point in generating a debug code to try to fix pi-hole.
169.xxx.xxx is the IP that the computer names itself after it can't find anything on the network. I'd suggest using manual IP config for now until you figure out the issue with your pc, or some day you'll re-install windows and I'm sure it will go away.
I should've modified my latest reply to better explain the situation, but all in all dhcp is not working at all. I did not notice this because I was logged on my vpn on my phone and it was not affected.
yep already did that. and after running pihole -r it finally worked.
but to no effect as dhcp is not working now. gonna format my sd and retry tomorrow from a fresh install. maybe I can spot what I did wrong along the way
You must have another Tux client available, your laptop maybe ?
Below one will release the current DHCP lease and acquire a new DHCP lease (showing details with the -v flag):
$ sudo dhclient -r; sudo dhclient -v
Killed old client process
Listening on LPF/wlan0/00:1f:3c:99:de:17
Sending on LPF/wlan0/00:1f:3c:99:de:17
Listening on LPF/eth0/00:1f:29:b1:f1:02
Sending on LPF/eth0/00:1f:29:b1:f1:02
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPREQUEST of 10.0.0.220 on wlan0 to 255.255.255.255 port 67
DHCPOFFER of 10.0.0.220 from 10.0.0.2
DHCPACK of 10.0.0.220 from 10.0.0.2
bound to 10.0.0.220 -- renewal in 33521 seconds.
EDIT: Oops I missed out on the screenshot you posted.
I'm out of ideas on that front.