Have you tried the FQDN for dc1?


*From:* [email protected] [mailto:
[email protected]] *On Behalf Of *J- P
*Sent:* Tuesday, June 03, 2014 1:43 PM
*To:* [email protected]
*Subject:* [NTSysADM] Extend DNS timeout



Hi all,

At one of our remote sites i have a 2008r2 server that was removed
(dcpromo/forceremoval ) because  the tunnel had been down for months.

We finally got the new router out there and although it is slow ( 512k /sat
)the tunnel is pretty stable,
the issue is that I now cannot join the server back to the domain;

It seems that the timeout period for DNS response is expiring before the
request can be responded to;
Ping Times are around 300ms from the remote site to ours


it can locate the SRV correctly , however, it cant locate a DC

the following domain controllers were identified by the query:
DC1
DC2
DC3
DC4
DC5
DC6
However no domain controllers could be contacted.

Common causes of this error include:

- Host (A) or (AAAA) records that map the names of the domain controllers
to their IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or
are not running.

NSLookup comes back in one of two ways

> DC1
Server: DC1
Address:  192.168.1.8

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to DNS.SERVER timed-out

OR
>DC1
 Server: DC1
Address:  192.168.1.8

*** DNS.SERVER can't find DC1: Non-existent domain



Jean-Paul Natola

Reply via email to