Windows Server - DNS Problem

Hi,

I have a local area network configured with windows server 2003, and all
computers connect to the internet through this server, using dns 192.168.0.4
which is on the windows server.
For some reason I can not connect to certain websites and for example I can
not connect to the shared calendars on outlook 2007 using that dns, if i
change the dns for example to another one like 208.67.222.222 it works.

can anyone explain me why??

Thanks!

JP

Hola Juan.
Tenes los forwaders bien configurados en el DNS del servidor? Para que
envien las peticiones al DNS de tu proveedor de Internet.

Please post the output of an nslookup for a problem host / domain
against both your internal and an external DNS servers.



Grant. . . .

Hola,

Gracias.
No se, como veo eso?

JP

Ok from Server:

nslookup

DNS requested timed out
timeout 2 seconds
*** Name server  for address 200.72.1.5 can not be found*** Timedout

Predetermined server: UnKnown
Address: 200.72.1.5



Client:

Microsoft Windows XP [Versión 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.



C:\Documents and Settings\ventas01>nslookup

*** No se puede encontrar el nombre de servidor para la dirección
192.168.0.4: N

on-existent domain (EN: Domain server for address 192.168.0.4 can not be
found  -- non existen)



*** Los servidores predeterminados no están disponibles (EN: Predetermined
servers are not available)

Servidor predeterminado:  UnKnown

Address:  192.168.0.4



Thanks

JP

I was actually hoping for you to do the following:

C:\>nslookup oma.yourdomain.tld 192.168.0.4

(Adjust "oma.yourdomain.tld" to match your server.)

And:

C:\>nslookup oma.yourdomain.tld 200.72.1.5

That way we can see what they (do not) resolve to internally and externally.

Also, what is your internal domain name?


You are welcome.



Grant. . . .

I see.

From the client i get this:

nslookup interpanel.cl 200.72.1.5

Servidor:  resolver.entelchile.net
Address:  200.72.1.5

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** La petición a resolver.entelchile.net a caducado (EN: The request to
resolver.entelchile.net has lapsed)


--
The server  name is interpanel.cl (that was long time ago, and we do not
host the website on this server)

JP

I also get timeouts trying to run the above command.

However I am able to run the following command.

nslookup interpanel.cl 4.2.2.2

I am not able to do any thing with DNS against 200.72.1.5.  I am
thinking that there is a chance that 200.72.1.5 is not allowing queries
from my IP address.


The fact that you got the two above lines and no errors, tells me that
your client was able to successfully query resolver.entelchile.net
(200.72.1.5).


This tells me that resolver.entelchile.net (200.72.1.5) most likely
filtered the query.

Are you allowed to query resolver.entelchile.net (200.72.1.5)?

WhoIs indicates that ns1.webhostingpad.com (216.239.133.52) and
ns2.webhostingpad.com (69.65.24.125) are authoritative for the
directly?

I was able to successfully query ns2.webhostingpad.com using the
following command:

nslookup interpanel.cl 69.65.24.125

interpanel.cl resolves to 204.93.163.124


Ok.

There is a web site by the interpanel.cl domain on 204.93.163.124.  So
I am not quite sure what to make of this.

Please re-try your DNS query against either 4.2.2.2 or 69.65.24.125.
I'd like to figure out if there is a larger DNS problem, or something
specific to the interpanel.cl domain.



Grant. . . .

Ifi do:

nslookup interpanel.cl resolver.
entelchile.net
Servidor:  resolver.entelchile.net
Address:  200.72.1.5

Respuesta no autoritativa:
Nombre:  interpanel.cl
Address:  204.93.163.124

And i also get:

C:\Documents and Settings\jpgallardo.INTERPANEL>nslookup interpanel.cl
4.2.2.2
Servidor:  vnsc-bak.sys.gtei.net
Address:  4.2.2.2

Respuesta no autoritativa:
Nombre:  interpanel.cl
Address:  204.93.163.124


Maybe 200.72.1.5 and .11 are not working.

JP

Hello Juan,

In a domain use only the domain DNS server on the NIC, so in your case i
assume the DC/DNS is the 192.168.0.4. All domain machines have to be configured
to use this as DNS server on the NIC, then either you can use the Forwarders
on the DNS server properties in the DNS management console, where you add
external DNS servers 4.2.2.2 and 4.2.2.1, or you use the root hints and update
them from an external DNS server.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

*nod*

Indeed it looks like that the servers you were querying was your problem.



Grant. . . .