Прочитал и понял только одно: тот хрен сам ничего не понял...20.03.04 00:08 Число просмотров: 1549 Автор: George Статус: Незарегистрированный пользователь
Обстановка: W2K,PDC.
Мой DNS стал выдавать предупреждаюшие сообщения, причину которых я не могу найти. Подскажите где рыть.
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 17.03.2004
Time: 11:47:39
User: N/A
Computer: TITANIC
Description:
The DNS server encountered a packet addressed to itself -- IP address 10.5.33.11.
The DNS server should never be sending a packet to itself. This situation usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
Example of self-delegation:
-> This DNS server dns1.foo.com is the primary for the zone foo.com.
-> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com,
(bar.foo.com NS dns1.foo.com)
-> BUT the bar.foo.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.
Data:
0000: 50 25 00 00 P%..
подробно о проекте
Анализ криптографических сетевых...
новое сообщение
закрытая нитка
новое сообщение
в закрытой нитке
старое сообщение
