rgreiner wrote:
> Hi,
>
> I'm getting a strange behavior with DNS using Monowall 1.235.
>
> All our clients are using monowall as their gateway and DNS.
>
> Monowall is configured as a DNS forwarder to our 3 real DNS servers
> (which are outside the monowall controlled network).
>
> When I'm on one of our windows client boxes command line and type
> "nslookup <some random server>", I get a timeout in the response. But,
> if a try to ping that name, open a web page, etc, it does resolve
> without problems. The Monowall server has a relatively high load, but
> it's not overloaded (the cpu usage stays usually between 20% and 50%,
> with a load of
>
> Does that make any sense to anyone? Did I miss something painfully
> obvious???
>
> Any help would be appreciated.
>
> Tks.
>
> -----------------------------
>
> Output sample from the nslookup:
>
> DNS request timed out.
> timeout was 2 seconds.
> *** Não é possível encontrar o nome de servidor para o endereço
> 172.16.0.1: Time
> d out
> *** Os servidores padrão não estão disponíveis
> Servidor: UnKnown
> Address: 172.16.0.1
>
> DNS request timed out.
> timeout was 2 seconds.
> DNS request timed out.
> timeout was 2 seconds.
> *** A requisição para UnKnown esgotou o tempo limite
>
> --------------------------
>
> ipconfig output
> Configuração de IP do Windows
>
> Adaptador Ethernet Conexão de rede sem fio:
>
> Sufixo DNS específico de conexão . : semfio.usp.br
> Endereço IP . . . . . . . . . . . . : 172.16.249.195
> Máscara de sub-rede . . . . . . . . : 255.255.0.0
> Gateway padrão. . . . . . . . . . . : 172.16.0.1
> ------------------------
>
> Monowall load:
>
> m0n0wall: execute command
>
> $ uptime
> 12:20PM up 1:21, 0 users, load averages: 0.21, 0.46, 0.46
>
>
>
You say m0nowall is is configured as a DNS forwarder to your 3 real DNS
servers. Have you verified that all three of these DNS servers are
actually working? I would test each one in the order you have them
listed in the m0n0wall configuration. | 