Did you set a static IP on the Pi using Network Manager?
If not, do so and this will ensure the Pi boots to the same IP each time, regardless of any DHCP server.
You also have multiple DHCP servers on your network, and only the second one (the Pi-hole) is passing out the IP of Pi-hole for DNS (192.168.1.101). They are also passing out conflicting domain names. Your router DHCP appears to be active and appears to be the first one.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 349 bytes from wlan0:192.168.1.254
Offered IP address: 192.168.1.101
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.254
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
router: 192.168.1.254
dns-server: 192.168.1.254
domain-name: "attlocal.net"
--- end of options ---
* Received 300 bytes from wlan0:192.168.1.101
Offered IP address: 192.168.1.208
Server IP address: 192.168.1.101
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.101
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.1.255
dns-server: 192.168.1.101
domain-name: "lan"
router: 192.168.1.254
--- end of options ---
DHCP packets received on interface wlan0: 2
Of note in your debug log (and not related to your problem), you have this entry in your adlists:
ads.servenobid.com
This is not the URL of an adlist. It is a domain, and it should be entered in your domains tab, not the adlists tab.