My remote office cannot request my DNS

[Rodolfo]

I have two networks

192.168.10.0 and 192.168.11.0. My DNS is located in the first network, all
machines can ping myADDomain.com. In my remote network I configured the DNS
with my AD DNS Server. The problem is this:

I can ping my DNS ip adrress but I can't ping myADDomain.com. (could not
find host) I can telnet my DNS Server with port 53.

Why my remote workstations cannot request DNS queries?

thanks

 

[Rodolfo]

For more info, this is what a 192.168.11.0 statios gives with nslookup

DNS request timed out.
timeout was 2 seconds
*** Can't find server nam
*** Default servers are n
Default Server: UnKnown
Address: 192.168.10.3

In a 192.168.10.0 this is the message

Default Server: DNSServerName.myADDOmani.com
Address: 192.168.10.3

 

[Kevin D. Goodknecht Sr. [MVP]]

In

For more info, this is what a 192.168.11.0 statios gives
with nslookup

DNS request timed out.
timeout was 2 seconds
*** Can't find server nam
*** Default servers are n
Default Server: UnKnown
Address: 192.168.10.3

In a 192.168.10.0 this is the message

Default Server: DNSServerName.myADDOmani.com
Address: 192.168.10.3

This is only a message from nslookup, which does a reverse lookup on the IP
of the DNS server it is using, that says it can't find the PTR record for
the IP of the DNS server. Hence, the "Can't find server name for address..."
you can ignore it, create a reverse lookup zone and PTR, or use a program
such as Dig or Netdig for DNS queries.
Netdig is my personal favorite with its Graphic User interface. There is no
commands to learn or remember, just set the server IP or name, the query
name, and record type from the drop down list and click resolve. Get it from
www.mvptools.com . It does require .NET framework be installed.

 

[Rodolfo]

I created a reverse zone 10.168.192. this works for my LAN. And I also
created and PTR to my DNS Server

I also created a 11.168.192 zone but it still doesn't work

 

[Rodolfo]

I used NetDig. When I use options RD and TCP this message is displayed:

opcode: Query, status: NOERROR, id: 42

flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

QUESTION SECTION:

acorde.or.cr. IN A

ANSWER SECTION:

myAdDomain.or.cr. 600 IN A 192.168.10.2

myAdDomain.or.cr. 600 IN A 192.168.10.3

Query time: 47 ms

Server : 192.168.10.3:53 tcp (192.168.10.3)

When : 26/08/2004 11:11:11 a.m.

Size rcvd : 62

but when I use UDP i have and error.



I still cannot log on my machine to my w2k domain

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I used NetDig. When I use options RD and TCP this message
is displayed:

opcode: Query, status: NOERROR, id: 42

flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0,
ADDITIONAL: 0

QUESTION SECTION:

acorde.or.cr. IN A

ANSWER SECTION:

myAdDomain.or.cr. 600 IN A 192.168.10.2

myAdDomain.or.cr. 600 IN A 192.168.10.3

Query time: 47 ms

Server : 192.168.10.3:53 tcp (192.168.10.3)

When : 26/08/2004 11:11:11 a.m.

Size rcvd : 62

but when I use UDP i have and error.



I still cannot log on my machine to my w2k domain

Open the UDP port.

 

[Rodolfo]

You mean in the routers right?

In


Open the UDP port.

 

[Kevin D. Goodknecht Sr. [MVP]]

In

You mean in the routers right?

All ports between your DCs should be open, 53 UDP is required for DNS. You
can make a TCP connection so something is blocking 53 UDP.

 

[Rodolfo]

Thanks a lot, it was the ISA Server Client

In

All ports between your DCs should be open, 53 UDP is required for DNS. You
can make a TCP connection so something is blocking 53 UDP.