2014-12-11 - Re: Local DNS problem

Header Data

From: Denilson Vinagre <de***e@gmail.com>
Message Hash: a2af1dcacd15f31d2125d8d6aedff13d2c7ffacb604d13c8cfa662087bd75fce
Message ID: <c9a69668-5b5d-4d04-885b-f54a3ccbf69f@grasehotspot.org>
Reply To: <ee86d208-e600-4292-a145-bf91d53cb025@grasehotspot.org>
UTC Datetime: 2014-12-11 03:57:57 UTC
Raw Date: Thu, 11 Dec 2014 02:57:57 -0800

Raw message 

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
>
>

Thread