{"action":"opened","issue":{"url":"https://api.github.com/repos/pi-hole/pi-hole/issues/643","repository_url":"https://api.github.com/repos/pi-hole/pi-hole","labels_url":"https://api.github.com/repos/pi-hole/pi-hole/issues/643/labels{/name}","comments_url":"https://api.github.com/repos/pi-hole/pi-hole/issues/643/comments","events_url":"https://api.github.com/repos/pi-hole/pi-hole/issues/643/events","html_url":"https://github.com/pi-hole/pi-hole/issues/643","id":174333139,"number":643,"title":"Forward intranet requests to router?","user":{"login":"colindean","id":197224,"avatar_url":"https://avatars.githubusercontent.com/u/197224?v=3","gravatar_id":"","url":"https://api.github.com/users/colindean","html_url":"https://github.com/colindean","followers_url":"https://api.github.com/users/colindean/followers","following_url":"https://api.github.com/users/colindean/following{/other_user}","gists_url":"https://api.github.com/users/colindean/gists{/gist_id}","starred_url":"https://api.github.com/users/colindean/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/colindean/subscriptions","organizations_url":"https://api.github.com/users/colindean/orgs","repos_url":"https://api.github.com/users/colindean/repos","events_url":"https://api.github.com/users/colindean/events{/privacy}","received_events_url":"https://api.github.com/users/colindean/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-31T17:35:17Z","updated_at":"2016-08-31T17:35:17Z","closed_at":null,"body":"I have an internal naming scheme, like `mylaptop.myhome.myname.com` and `mynas.myhome.myname.com`.\r\n\r\n##### Expected Behaviour:\r\n\r\nWhen I visit `mynas.myhome.myname.com`, I expect it to resolve and load.\r\n\r\n##### Actual Behaviour:\r\n\r\nMy internal domain no longer resolves. The pihole seems to do the external lookup.\r\n\r\n##### Steps to reproduce this issue:\r\n\r\nFresh, ootb configuration, with my router sending the pihole and the router as DNS servers in that order.\r\n\r\n##### The central question\r\n\r\nCan I do one of:\r\n\r\n1. Configure my router to tell clients to ask it for DNS first and for internal domains only?\r\n2. Somehow have the router point to the pihole for DNS? I think the latter is doable and I'm going to try that this evening.\r\n3. Have the pihole forward requests to the router when it fails a lookup? \r\n\r\nI'm using an ASUS RT-N66U running a recent build of Merlin firmware, if that matters. I'm not afraid to tinker!"}}
{"actor":{"display_login":"colindean"}}