Seeing IP addresses rather than names

The issue I am facing:
ASKING ONLY.
When I go to my logs - don't do it often.
Torn between that is ok and being paranoid and checking them constantly.
PiHole is NOT the DHCP server.
Looking at my logs all/most machines show their names rather than their IP address.

I have an NVIDIA shield (media player) and when it is used I see its IP address and not its name.

I accept it could be it is dumb but why are other devices honoring their assigned names I set in the DHCP server?

Details about my system:
Multi VLAN network.
The Media player is on a separate VLAN to most other machines.
DHCP is done by a Ubiquity Edge router.

What I have changed since installing Pi-hole:
As stated, I am just curious why I am not seeing the NAME but am seeing the IP address instead.

Have I missed any needed information?
(Sorry very low level user and I try to leave well enough alone.
If it isn't broken....... sort of thing. And AFAIK, it isn't broken.)

Does it always show up with the same IP address?

And please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

(Sorry it took so long.)

Log - attached.
I hope I did it right.

Oh, IP number:
I have the DHCP server set to assign the same IP address to it, so I would hope that is happening.

Annoying that when I click the upload button and scan for the LOG file, those kind of files are NOT shown and so I have to rename it.

When it was being made I did also see a bit of red text - problems?
I'll look at the file myself, but if you notice anything else of concern, please let me know.

(Moderator edit: explicit debug log removed)

For your own privacy and security, do not post your debug log publically.

We've been through this a few times with you already:
We would require only the debug token as shown at the end of the process when you allow uploading:

Thank you for sharing your hopes.
Doesn't answer my question, though:

Sorry.

I hope / believe there is nothing too private in there.

Which question did I miss in answering?
(I'm online just now so I hope I can help you help me.)

The IP address assigned to it is always the same.

But the DHCP server is NOT the PiHole machine.

Substituting <shield.ip> with that IP address of your NVIDIA shield, what is the output of

nslookup <shield.ip> 
nslookup <shield.ip> 192.168.17.1

nslookup 192.168.12.5 192.168.17.1
5.12.168.192.in-addr.arpa name = Shield.Marys-Farm.

IP reversed.

That doesn't seem like the full output, and it is also just the output from one of the commands.

Well, that's what I typed and what I got back.

Screen shot how.

Ubuntu 22.04 LTS

That's still only one command outpout.
It looks ok - your router is able to provide a name for your shield's IP.

How about the other command's output?

Sorry, which other command.
(I may need glasses.)

Oh, sorry.....

The first line.
I read that as a template.

Hang on.

Hmmm...
Interesting.
Shield on.

nslookup 192.168.12.5
** server can't find 5.12.168.192.in-addr.arpa: NXDOMAIN

That would suggest that the default DNS server (likely, your Pi-hole) of your me-desktop machine does not know a name for that IP.

Please run the lookup via your Pi-hole's IP:

nslookup 192.168.12.5 <pi.ho.le.ip>
nslookup 192.168.12.5 192.168.17.23
** server can't find 5.12.168.192.in-addr.arpa: NXDOMAIN

192.168.17.23 is PiHole's IP address.
(This may be the problem?)

(Sorry, I see you are replying and I don't want to complicate things.)

This is how I have the DNS set up for that network.

Yes, quite likely.

Enabling Pi-hole's Conditional Forwarding should address your issue.
As you have multiple subnets (due to VLANs), you may not be able to fully configure that through Pi-hole's UI alone.

Nevertheless, give the following settings a try:
192.168.0.0/16 - 192.168.17.1 - Marys-Farm

That would cover different 192.168.x.x networks, but not others like 10.0.0.0, and obviously, it also wouldn't cover different domain names for your different VLANs.

Alternatively, you could try to configure your router as Pi-hole's only upstream.
You'd also want to untick Never forward reverse lookups for private IP ranges in Pi-hole's DNS settings for that to work, and probably untick Never forward non-FQDN A and AAAA queries as well.

Not trying to be difficult,

Don't I already?
(Yes, I know I should know.)
I have (not that recently) done a bit of network restructure.
But to the best of my knowledge I thought the router is the uplink address.
(Though there is a managed switch between them.)

Arching back to the first bit:

192.168.0.0/16 - 192.168.17.1 - Marys-Farm

Sorry, lost me.
Just saw the edit come up.
I'll post this to not get too confused.

Your debug log suggests you are currently using 9.9.9.9 and 149.112.112.10 as Pi-hole's upstreams.

Sorry.... My mistake.

DNS servers. (I can't don't (see?) always parse things as they are meant.)

But.....
(Confused)
I have some VLANS - as I am sure you can see - and their DNS is the router because I can't put PiHole's IP as their DNS as it is in/on a different network. (All but one)

So the router is needed - as it has access to all VLANs.
Forgive my ignorance.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.