Sorry last minute canges!
I changed some 
Will the entries here no longer show the hostname/device name? And are the NXDOMAIN replies normal?
EDIT: The query log is also still showing .local for many entries:
It might be that you have to renew your clients DHCP leases before you see names changing.
Usually that happens when you dis and reconnect them to network (EDIT: or have to wait a long time before they do it themselves).
Otherwise reboot them.
Also you can check what hostname your DHCP service holds/knows about for a particular IP with below:
dig +short @192.168.1.1 -x <CLIENT_IP_ADDRESS>
Eg:
pi@ph5a:~ $ dig +short @10.0.0.4 -x 10.0.0.11
hakpc.home.dehakkelaar.nl.
Thats where Pi-hole gets the names from and refreshes them every hour.
If dont get a reply no names.
EDIT: Also at the bottom you have the "Flush network table" button:
This seems to work for some devices, but not all:
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.6
RokuStreamingStick.iot.home.arpa.
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.16
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.6
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.5
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.12
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.113
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.13
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.15
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.2.13
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.1.122
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.1.122
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.40
HAL-002-153f6710.iot.home.arpa.
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.41
PUR-002-a986de59.iot.home.arpa.
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.42
MyQ-BFF.iot.home.arpa.
root@DietPi:~# dig +short @192.168.1.1 -x 192.168.3.16
Have you renewed DHCP leases for them?
Yeah, I reconnected them all and even rebooted the access point they all are connected to.
They have to acquire IP detail automatically via DHCP or otherwise they wont advertise their hostname to the DHCP service (your router).
Not manually statically assigned!
Can flush the network table and wait for an hour.
I did flush the network table a bit ago. But, I will wait for them to renew on their own 
Thank you very much for your help tonight! Hopefully a mod chimes in about the Pihole not blocking things in the adlists and we can close the whole loop here, haha.
What does below show?
pihole-FTL sqlite3 --header --column /etc/pihole/gravity.db "SELECT * FROM adlist"
root@DietPi:~# pihole-FTL sqlite3 --header --column /etc/pihole/gravity.db "SELECT * FROM adlist"
id address enabled date_added date_modified comment date_updated number invalid_domains status
-- ----------------------------------------------------------------------------------------- ------- ---------- ------------- -------------------------------------- ------------ ------ --------------- ------
1 https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts 1 1596221052 1691110086 Migrated from /etc/pihole/adlists.list 1691108393 205107 1 1
3 http://sysctl.org/cameleon/hosts 1 1596221052 1691110088 Migrated from /etc/pihole/adlists.list 1691108397 20561 0 1
4 https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt 1 1596221052 1691110091 Migrated from /etc/pihole/adlists.list 1691108398 34 0 1
5 https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt 1 1596221052 1691110094 Migrated from /etc/pihole/adlists.list 1691108398 2701 0 1
6 https://reddestdream.github.io/Projects/MinimalHosts/etc/MinimalHostsBlocker/minimalhosts 1 1596221052 1691110097 Migrated from /etc/pihole/adlists.list 1691108398 710 0 1
7 https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt 1 1596221052 1691110100 Migrated from /etc/pihole/adlists.list 1691108399 2735 1 1
8 https://raw.githubusercontent.com/crazy-max/WindowsSpyBlocker/master/data/hosts/spy.txt 1 1596221052 1691110102 Migrated from /etc/pihole/adlists.list 1691108400 347 0 1
9 https://www.github.developerdan.com/hosts/lists/amp-hosts-extended.txt 1 1596221052 1691110104 Migrated from /etc/pihole/adlists.list 1691108401 16452 0 1
10 https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt 1 1596221052 1691110106 Migrated from /etc/pihole/adlists.list 1691108403 42536 0 1
11 https://raw.githubusercontent.com/Firestorrrm/Minimal-Hosts-Blocker/master/iosadlist.txt 1 1596221052 1691110108 Migrated from /etc/pihole/adlists.list 1691108404 30648 1 1
12 https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/SmartTV.txt 1 1596221052 1691110114 Migrated from /etc/pihole/adlists.list 1691108407 242 0 1
13 https://raw.githubusercontent.com/Sekhan/TheGreatWall/master/TheGreatWall.txt 1 1643441259 1691110117 1691108407 132 1 1
14 https://raw.githubusercontent.com/oneoffdallas/dohservers/master/iplist.txt 1 1643441296 1691110070 1691108407 668 55 1
16 https://gist.github.com/sidward35/cea28bedd0ec0b1bceec8c2b22c163c4 1 1690979976 1691110055 1691108408 1 981 1
18 analyticsengine.s3.amazonaws.com 1 1691023479 1691023479 1691108409 0 2 1
And below ones:
pihole -q adsfs.oppomobile.com
nslookup adsfs.oppomobile.com localhost
And what do the logs show when do that nslookup query:
pihole -t
root@DietPi:~# pihole -q adsfs.oppomobile.com
Match found in exact blacklist
adsfs.oppomobile.com
Match found in https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts:
adsfs.oppomobile.com
Match found in https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt:
adsfs.oppomobile.com
root@DietPi:~# nslookup adsfs.oppomobile.com localhost
Server: localhost
Address: 127.0.0.1#53
Name: adsfs.oppomobile.com
Address: 0.0.0.0
Name: adsfs.oppomobile.com
Address: ::
pihole -t
**Aug 5 23:11:16: query[A] adsfs.oppomobile.com from 127.0.0.1** **Aug 5 23:11:16: exactly blacklisted adsfs.oppomobile.com is 0.0.0.0** **Aug 5 23:11:16: query[AAAA] adsfs.oppomobile.com from 127.0.0.1** **Aug 5 23:11:16: exactly blacklisted adsfs.oppomobile.com is ::**
These show this URL is being blocked by the Pi-hole for sure...but why was it not blocked last night?
They dont seem to appear being blocked via the ad/block lists but blacklisted instead.
This is blocked:
Did you enter blacklist entries/regex'es?
Looks like they're all being blocked now. The only thing we changed were the domain changes we made tonight.
Not that I'm aware of or remember doing for this specific domain. I did add some regex blocks but that was for other targeted blocking. Not for this domain.
EDIT: Ah, just looked again. I guess I did blacklist some of these from when we were testing last night. My mistake. I just deleted them from the blacklist and then did an nslookup on them and the query log returned:
So you're right. The Pi-hole isn't blocking these still.
Do the mods/devs still need to checkup?
Maybe mark a solution?
Just made an edit to my previous reply.
With all the changes, also upload a new token for the mods/devs to have a look pls?
Yeah, good call -
1 Like
I just thought of something...I have these hostnames hardcoded into the /etc/hosts file. And every name in the file is appended with .local. This is why the Pi-hole is still showing this domain.
Hah!
I did this long ago to force the Pi-hole to show the hostnames of all the devices on the network.
Since I have all of my devices statically assigned, should I manually append the new domains to each of the devices in /etc/hosts?
EDIT: Actually, having a domain manually appended at the end of a hostname doesn't seem to be necessary.