Forward intranet requests to router?

[colindean]

I have an internal naming scheme, like mylaptop.myhome.myname.com and mynas.myhome.myname.com. myname.com resolves publicly, but only my router resolves myhome.myname.com and only internally.

Expected Behaviour:

When I visit mynas.myhome.myname.com, I expect it to resolve and load.

Actual Behaviour:

My internal domain no longer resolves. The pihole seems to do the external lookup.

Steps to reproduce this issue:

Fresh, ootb configuration, with my router sending the pihole and the router as DNS servers in that order.

The central question

Can I do one of:

1. Configure my router to tell clients to ask it for DNS first and for internal domains only?
2. Somehow have the router point to the pihole for DNS? I think this is doable and I'm going to try that this evening.
3. Have the pihole forward requests to the router when it fails a lookup?

I'm using an ASUS RT-N66U running a recent build of Merlin firmware, if that matters. I'm not afraid to tinker!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[PromoFaux]

I'm not afraid to tinker!

Then we'll begin..!

This SHOULD be an easy fix actually, but i might be wrong. You can try adding the host names to /etc/hosts on the pihole machine. e.g:

192.168.1.1    mylaptop    mylaptop.myhome.myname.com
192.168.1.2    mynas    mynas.myhome.myname.com

followed by a sudo service dnsmasq restart and seeing if your client devices resolve then...

[diginc]

If your router is still searching & resolving hostnames on your domain/network (1) then you may be able to forward the entire subdomain (2) onto your router from your pihole. Saving you the step of having to add each DNS entry manually for new PCs or DHCP IP changes.

(1)

# If this works against your router
$ host pc.myhome.myname.com 192.168.1.1

(2)

# Add a file like this
$ cat /etc/dnsmasq.d/forward_internal_domain_to_router.conf
server=/myhome.myname.com/192.168.1.1

# And then after a dnsmasq restart this
$ host pc.myhome.myname.com pi.hole
# should work forward/delegate the request to the router, 

note: $ are commands issued, # are comments, no prefix = return value

[PromoFaux]

Of course! I was just looking up the server=/x.y.z/1.2.3.4 for soemthing else. Should have clicked then!

[colindean]

Adding `server=/myhome.myname.com/192.168.1.1.` to `/etc/dnsmasq.d/forward_internal_domain_to_router.conf` did it! It’d be nice to have a GUI or command line way to do that easily. I’m surprised that this problem hasn’t come up previously.

[colindean]

It looks like in this particular instance, pi.hole is getting blocked, too?

[AzureMarker]

That's normal behavior. We can only tell if a domain is blocked if the resolved ip is the Pi-hole's. We could manually exclude that domain from the blocked ones.

[colindean]

What's interesting is that http://pi.hole/admin resolves at the command line but not in my browser. Maybe my browser's DNS cache is stale?

[AzureMarker]

Command line and browser on the same computer? If so, check out how to clear browser cache. Chrome has it at chrome://net-internals/#dns

[colindean]

It apparently expired while I was away. I didn't even need to flush manually. Working fine now!

[AzureMarker]

Is this issue fixed now?

[colindean]

Yeah, but I think maybe a feature request has come out of it: the ability to add that forwarding line through the command line or the web interface. That, and it documented, would have prevented this thread from occurring, for the most part.

[AzureMarker]

Ok. You can make an issue on the admin repo, flag as feature request, and link to this issue.

[AzureMarker]

Also, maybe I'll flag this one as a feature request too, since I have a feeling that the command line should be the one to actually contain the functionality. The web interface could be just a front for the command line, like whitelisting and blacklisting.

[trulleberg]

Not sure if this is the right place, maybe we it should also be possible to forward local requests to the local router?
like:
server=/fritz.box/178.168.192.in-addr.arpa/192.168.178.1

this should make sure that all requests for my local domain and reverse (ip to dns) lookups in my subnet are send to the local router.

[AzureMarker]

Set your router as an upstream DNS server, if it is smart enough to support that. Otherwise, try using Pi-hole's DHCP instead of the router's. Then hostnames are automatically available to Pi-hole (and set new ones in /etc/hosts).

[trulleberg]

Hey,
I did configure my router as upstream DNS, but lookups for private IPs failed!

I think the "bogos-priv" prevents requests from private IPs to be sent to upstream DNS Servers.
So as workaround I removed the bogus-priv from /etc/dnsmasq.d/01-pihole.conf, restarted dnsmasq and it works.

[DL6ER]

Well ...

You may have to apply this bug fix to have it actually passed to dnsmasq (will be fixed in the next release):
https://github.com/pi-hole/pi-hole/pull/1099/files

[DL6ER]

Fully implemented in admin interface v2.3