Client hostnames show "unknownXXXXXXXXXXXX.attlocal.net" on ATT RG

[BBrendan]

Hello,

I am running pihole with an ATT RG
pihole is running fine and is blocking ads as expected, but I'd like some more detail on the clients so that I can fine-tune the blocked domains.
Unfortunately the local hostnames do not appear to be resolving. Would anyone know why this is? How can I get these hostnames to resolve properly?

I have disabled IPv6 and DHCP on the RG.

Expected Behaviour:

Local hostnames should resolve, and appear to resolve in DHCP settings:

Actual Behaviour:

Local hostnames in Query log and Dashboard show "unknown.attlocal.net" :

This is also seen in the ATT RG Status page:

Thanks in advance!

[yubiuser]

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

[BBrendan]

Thanks for the help!

Looks like this issue was due to ATT hijacking DNS lookups:

https://gist.github.com/CollinChaffin/24f6c9652efb3d6d5ef2f5502720ef00

Disabling this setting resolved the issue.

[LilRedDog]

Yes!

I have had that same issue.

I only used the gateway as passthrough and then used my router to manage DHCP and Pi-hole for DNS.

AT&T gateways are controlled by AT&T. Unless they are configured to passthrough.

I am only replying to get this to hit other inquires.

If you have this issue it is because AT&T gateway/routers do not care how you configure them.

Get a router that can have opensource firmware installed and let it OWN the LAN.

I prefer OpenWRT but the configuration is persnickety and the open support is, often, not tolerant of newbies.

[BBrendan]

I agree in principle. Telecom providers shouldn't hamstring end users by locking out options. But your post completely derails the OP.

It is not necessary to run your own router to fix this specific issue.

[LilRedDog]

In all earnest:
How did I derail the OP when I agreed with their fix?
AT&T gateways can do whatever they want. It CAN be the best solution to not use one's provider's gateway as a router.

That cfg worked for them but it is not the best solution. IMHO.

I'm trying to learn how to navigate in here.
It is not going well and I would appreciate all the help I can get.

Their AT&T router is phoning home and they want to know how to fix it.
All I did, was give a different answer because I do not trust AT&T; I have posted before that AT&T was bypassing, randomly, because I had a configuration mistake..
And AT&T can reconfigure their gateway anytime they want to.
When that happens, they will be back here again asking why.

I, really, do not understand; why I am getting so much heat?

edit

Well crap, you are the OP and you are upset.
Usually OP means "Original Poster",

Had no idea it was you.

I apologize for trying to help, you more.
My bad.

2nd edit...

and after reading all of the link you provided:

Not all AT&T gateways allow your 'opt-out'.

brbeaird commented on Jun 10, 2020

Opting out of the preference does not work for me. I waited a week and tried a hard modem reset. AT&T support finally got back to me and said my particular modem (BGW 210) does not currently support the opt-out command. This is giving me all kinds of headaches working from home over VPN. For now, I have manual DNS settings on my machine, but I still run into weird issues sometimes. Really wish there was a way I could totally disable this awful setting.

So, now I stand by my post.