Selfhosted

40716 readers

454 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

PiHole local DNS Config understanding issues (self.selfhosted)

submitted 1 year ago* (last edited 1 year ago) by nexusband to c/selfhosted

6 comments fedilink hide all child comments

Hi,

been running PiHole with my FritzBox as DHCP Server for a while now. Just got Fibre and the new router doesn't support "only" setting an upstream DNS (neither does it support setting a domain suffix/local domain). I've switched the DHCP off and now PiHole does DHCP as well.

The FritzBox and the new Router added the domain suffix to recognized hostnames automatically, so even if i set up a fixed IP-Address on some device or machine, i could always use the hostname.local.domain without having to set a reservation.

Can PiHole/AdGuard/Technitium even do this? Do they need some extra configuration? PiHole does recognize the Hostnames correctly for some devices, but most are missing: For example, my Proxmox host was reachable with "pve.domain.local", it isn't with PiHole, even though PiHole identified the hostname. My Homeassistant isn't recognized at all, even though the IP-Address is showing up in PiHole. The Domain under "Advanced DHCP Settings" is set up.

Am i misunderstanding something or did i configure something wrong?

Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago (1 children)

If your pihole is acting as the dhcp server, you should only need the domain set up under the advanced dhcp settings, and it appends the domain to the hostname whenever a dhcp lease is assigned.

You may have some responses from .local addresses that are not registered in dhcp since .local is used with mDNS

Alternatively, if you still have the dchp server running on one of your other boxes and you have two dhcp servers, you may be getting clients leasing from the wrong server, and in that case pihole would not know about it. If you have a different domain name set up in another dhcp server you want pihole to resolve, you can set up conditional forwarding (on the DNS settings tab) in order for pihole to know where to ask about that domain

You could also add clients manually under 'DNS Records', and you can assign whatever domain, but that's also very manual and shouldn't be needed if pihole is assigning leases and you have the domain set up properly

[–] nexusband 1 points 1 year ago (1 children)

DHCP leases work - they are also correctly registered with the Hostname, it's just those that have a static IPv4 configured (outside the DHCP range of course) It also does work for some, but for Homeassistant and PVE for example it does not...

[–] [email protected] 2 points 1 year ago

Are you saying that it's not working for things that have static leases, but are for dynamic? How are they being assigned? Do you have them set statically from the dhcp server, or from the end device? If it's assigned on the end device, then I don't think pihole ever picks up the hostname since that would have been sent in the dhcp discovery, and if it's static on the end device, it won't ever issue a dhcp discovery message. So it would need to be manually added to your local DNS if it's assigned static on the device