Периодически падает, потом сам становится. Без моего вмешательства. Чего я только не делал.
С утра проверяю, все путем.
Типичные ивенты:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 05.06.2006
Time: 15:02:10
User: N/A
Computer: S01
Description:
DNS server has updated its own host (A) records.
In order to ensure that its DS-integrated peer DNS
servers are able to replicate with this server, an
attempt was made to update them with the new records
through dynamic update. An error was encountered during
this update, the record data is the error code.
If this DNS server does not have any DS-integrated peers,
then this error
should be ignored.
If this DNS server's Active Directory replication partners do not
have the correct IP address(es) for this server, they will be unable
to replicate with it.
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server,
add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00 ?...
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 05.06.2006
Time: 14:48:46
User: N/A
Computer: S01
Description:
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly.
The extended error debug information (which may be empty) is "0000208F: NameErr: DSID-031001B3, problem 2006 (BAD_NAME), data 8350, best match of:
'DC=,cn=MicrosoftDNS,cn=System,DC=service,DC=local'".
The event data contains the error.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 00 "...
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 2630
Date: 05.06.2006
Time: 14:30:22
User: N/A
Computer: S01
Description:
The DNS server could not configure the network connections of
this computer with the local computer's IP address as the preferred DNS server,
because this computer is connected to networks with different or invalid DNS namespaces. Manual configuration of the local DNS server to perform name resolution on one or more of the namespaces is required before the preferred
DNS servers of this computer should be modified.
If the network connections of this computer are not configured with the local computer's IP address as the preferred DNS server, this computer may not be
able to dynamically register DC locator records in DNS. Absence of these records may prevent other Active Directory domain controllers and domain members from locating this domain controller.
User Action:
Ensure that DC locator DNS records enumerated in the file %SystemRoot%\system32\config\netlogon.dns are registered on the local DNS server. If these records are not registered in DNS:
a) Add a delegation to this DNS server to parent DNS zone matching the name of the Active Directory domain OR
b) Configure the local DNS server with appropriate root hints and forwarders
(if necessary) and configure the network connections of this computer with the local computer's IP address as the preferred DNS server. Note that other computers using other DNS servers as their preferred or alternate DNS servers
may not be able to locate this domain controller, unless the DNS infrastructure is properly configured.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 00 00 00 W...
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 05.06.2006
Time: 14:28:42
User: N/A
Computer: S01
Description:
The DNS server machine currently has no DNS domain name.
Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com").
You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.
While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname. This can lead to incorrect and failed referrals when clients
and other DNS servers use these records to locate this server by name.
To correct this problem:
1) open Control Panel
2) open System applet
3) select Computer Name tab
4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
5) reboot to initialize with new domain name
After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name. However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Конфигурация сети:
S01.service.local (PDC, Windows 2003 Server Standard):
WAN-ADSL:
IP:192.168.1.2 (assigned by DHCP/ADSL modem)
DNS server: 192.168.1.1 (local.gateway)
Default gateway: 192.168.1.1
LAN-NAT:
IP:192.168.3.1 (manually configured)
DNS Server: 192.168.1.2 (s01.service.local)
Default gateway: 192.168.1.1
Сервисы: AD DC, DHCP, NAT, DNS
S02.service.local (Additional DC, Windows 2003 Server Standard):
Indoor:
IP:192.168.3.10 (assigned by DHCP)
DNS server: 192.168.1.2 (defaul server: s01.service.local)
Default gateway: 192.168.3.1
DHCP server: 192.168.3.1
Outdoor:
IP:192.168.4.1 (manually configured)
DNS Server: 192.168.1.2 (s01.service.local)
Default gateway: 192.168.3.10
Сервисы: AD DC, DHCP, NAT
S03.service.local (standalone, Windows 2003 Server Standard):
LAC1:
IP:192.168.3.11 (assigned by DHCP)
LAC2:
IP:192.168.5.1 (Manual,WinRoute)
и т.д.
ЗЫ.В сети около 80 клиентов
