2014-12-11 - Re: [GRASE-Hotspot] Re: Local DNS problem

Header Data

From: Denilson Vinagre <de***e@gmail.com>
Message Hash: 9a5beb0b262b03719e3419e7bdf84aa3c56faa5471fe01dc1d22594c5c8e7831
Message ID: <cb40c6cc-ca80-423f-8bcd-e8a0223c49db@grasehotspot.org>
Reply To: <CAESLx0LR3XPodiv3nEyr_0skrw5__FkTQ8AghVvZZgZC-ac=DQ@mail.gmail.com>
UTC Datetime: 2014-12-11 04:50:34 UTC
Raw Date: Thu, 11 Dec 2014 03:50:34 -0800

Raw message 

Hi Tim,

Thanks for your reply.

That's what we were expecting to happen but, sadly, it is not.

As per our tests, from the console of the Grase machine we can do local DNS 
resolution just fine, all connectivity tests to the AD DC work perfectly, 
but when we try the exact same nslookups from one of the PCs, pointed at 
Grase for name resolution, the requests time out. However, Internet names 
resolve just fine from the PCs.

What might we have done wrong and where might we look for the source of the 
issue?

Thanks again,

Denilson Vinagre


Quinta-feira, 11 de Dezembro de 2014 12:16:18 UTC+1, timwhite88 escreveu:
>
> Grase sets all clients to point to itself for DNS, and then forwards to 
> which ever DNS server you have specified in the Admin pages.
> If you set this "upstream" DNS server to be the AD server, the clients 
> should get the correct DNS results.
>
> Tim
>
> On Thu, Dec 11, 2014 at 8:57 PM, Denilson Vinagre <de***.@gmail.com 
> <javascript:>> wrote:
>
>> At Grase DHCP only has the option to change the dns that Grase is 
>> forwarding.
>>
>> How can I set DNS at Grase DHCP? it currently set's the DNS server to 
>> 192.168.20.4 automatically for the pcs.
>>
>> Thanks.
>>
>>
>>
>> Quinta-feira, 11 de Dezembro de 2014 11:00:21 UTC+1, Denilson Vinagre 
>> escreveu:
>>
>>> I have grase working with the following network configuration:
>>>
>>> ISP --> modem -->  switch --> grase --> PCs
>>>                                  |
>>>                   Windows server with Active Directory Domain
>>>
>>> - The PCs receive IP addresses from grase in the 192.168.20.0 range
>>> - Default gateway is grase at 192.168.20.4
>>> - Default DNS server is also grase
>>> - Windows server at 192.168.20.30 does local DNS resolution along with 
>>> fowarding to external DNS
>>> - Grase gets DNS resolution from 192.168.20.30
>>>
>>> Problem:
>>> I am able to access interne resources but cannot access local resources, 
>>> so users unable to login to active directory.
>>>
>>> Other Info:
>>> - DNS lookups for local resources from grase using 192.168.20.30 as DNS 
>>> server are sucessful
>>> - DNS lookups  for local resources from the PCs fail.
>>>
>>> How can I make grase forward DNS request to Windows server?
>>>
>>> Thanks 
>>> Denilson Vinagre
>>>
>>>  -- 
>> This mailing list is for the Grase Hotspot Project 
>> http://grasehotspot.org
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Grase Hotspot" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to gr***.@grasehotspot.org <javascript:>.
>> To post to this group, send email to gr***.@grasehotspot.org 
>> <javascript:>.
>> Visit this group at 
>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit 
>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/c9a69668-5b5d-4d04-885b-f54a3ccbf69f%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/c9a69668-5b5d-4d04-885b-f54a3ccbf69f%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>

Thread