DNS Event 1000

  • Thread starter Thread starter Lance
  • Start date Start date
L

Lance

Ok, I thought I had everything setup right, but naturally
when the power went out, I found out differently!

Our setup:
All Windows 2000 Servers

Primary domain: domain.com
Secondary domain: us.domain.com

32 Remote locations serving approx 15 people

Each remote site has a Windows 2000 server configured as
a DC, DNS and Global Catalog of the us.domain.com

DNS is AD integrated.

Our main office contains the FSMO PDC / Schema, etc. All
remote sites are configured (in TCP/IP) to use the main
office as their primary DNS and themselves as secondary
DNS servers.

Naturally, when the power went out at the main site, all
of our remote sites began to get these errors:

Source: Userenv
Event ID: 1000
Windows cannot establish a connection to us.domain.com
with (0).

Followed by:
Source: Userenv
Event ID: 1000
Windows cannot query for the list of Group Policy
objects . A message that describes the reason for this
was previously logged by this policy engine.


All remote users were not able to login - this was a
problem. Refering to this URL, I thought I had
everything setup correctly:

http://support.microsoft.com/?kbid=291382

Any advice would be appreciated!

Thanks,

Lance
 
In
Lance said:
Ok, I thought I had everything setup right, but naturally
when the power went out, I found out differently!

Our setup:
All Windows 2000 Servers

Primary domain: domain.com
Secondary domain: us.domain.com

32 Remote locations serving approx 15 people

Each remote site has a Windows 2000 server configured as
a DC, DNS and Global Catalog of the us.domain.com

DNS is AD integrated.

Our main office contains the FSMO PDC / Schema, etc. All
remote sites are configured (in TCP/IP) to use the main
office as their primary DNS and themselves as secondary
DNS servers.

Naturally, when the power went out at the main site, all
of our remote sites began to get these errors:

Source: Userenv
Event ID: 1000
Windows cannot establish a connection to us.domain.com
with (0).

Followed by:
Source: Userenv
Event ID: 1000
Windows cannot query for the list of Group Policy
objects . A message that describes the reason for this
was previously logged by this policy engine.


All remote users were not able to login - this was a
problem. Refering to this URL, I thought I had
everything setup correctly:

http://support.microsoft.com/?kbid=291382

Any advice would be appreciated!

Thanks,

Lance
Click to expand...

May want to try to use the remote location's DNS on those servers as the
first entry and the home office as the second. Reduces WAN traffic. For
registration requests, they will be sent to the server with the Primary zone
by the MNAME record. So when the power went out, it was probably querying
the first entry, which is the home office.

Confirm that the SRV records still exist on the Primary zone.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
In Lance <[email protected]> posted their thoughts, then I offered mine

May want to try to use the remote location's DNS on those servers as the
first entry and the home office as the second. Reduces WAN traffic. For
registration requests, they will be sent to the server with the Primary zone
by the MNAME record. So when the power went out, it was probably querying
the first entry, which is the home office.

Confirm that the SRV records still exist on the Primary zone.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================


.
Click to expand...

Thanks for the input. I did check the srv records for
both domain.com and us.domain.com at the remote site, and
everything looks good. Just a question about the DNS
order in the IP stack (on the remote server, which is a
DNS server), if the primary DNS is the IP of the DNS
server at the main office and the secondary is its own
IP, shouldn't the query time out on the primary DNS (when
the power went out in Michigan) and it roll over to the
secondary?

Thanks again!

Lance
 
Back
Top