problem sa dns serverom

[ gogi100 @ 21.06.2009. 16:09 ] @

imam mrezu pod win 2003 na kome mi je smesten i dns server i dhcp i domain controller. Klijent racunari su pod win xp pro. Svi oni rade ok, pristupaju resursima,ali kad otovrim konzolu dns i pogledam dns logove non stop mi se pojavljuju greske

Code:

EVENT message 7062:
DNS Server encountered a packet addressed to itself -- IP address<actual IP address>. 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 DNS server.

Code:

Kod:
Event ID    9999
Source    DNS
Type    Warning
Description    DNS Server has encounters numerous run-time events. These are usually caused by the reception of bad or unexpected packets, or from problems with or excessive replication traffic. The data is the number of suppressed events encountered in the last 15 minute interval.

Kako da resim ovaj problem? Kad ukucam na primer na jednoj klijent masini nslookup 127.0.0.1 dobijem

Code:

*** Can't find server name for address 127.0.0.1: Timed out
*** Default servers are not available
Default Server: Unknown
Address: 127.0.0.1

Napomena: ja sam ranije radio replikaciju i izvrsio kompletno prebacivanje active directory dns i dhcp-a sa starog na novi server. U DNS konzoli na primer u stavci dns servera neame server stoje adrese oba servera i na jos par mesta. Da to mozda ne pravi problem, pa mi se pojavljuju poruke event id 7062 i 9999

Hvala

[ valjan @ 22.06.2009. 08:16 ] @

Posto ti je DC ujedno i DNS server, onda prvo i najvaznije pravilo koje moras da ispostujes je da u TCP/IP Properties LAN konekcije svih klijenata, kao DNS stoji iskljucivo DC i nijedan drugi server (naravno, ako imas vise DC-ova u domenu, PDC stavis kao primarni DNS a BDC-ove kao sekundarne DNS-ove). Posto kazes da imas DHCP, pretpostavljam da preko njega svim klijentima podesavas koji DNS server da koriste, pa proveri sta je podeseno na DHCP-u i ispravi sva neispravna podesavanja. Takodje, u TCP/IP Properties LAN konekcije DC-a treba da stoji samo on kao DNS (ne 127.0.0.1 nego njegov IP koji vide i ostali racunari u mrezi).

Druga bitna stvar je da DNS tvog provajdera ne sme nigde da se pojavi osim u Forwarders listi tvog DNS servera. U Forwarders listi ne bi trebalo da stoji nijedan drugi server, narocito ne DC iz tvog domena.

Treca stvar bitna za AD je da Reverse Lookup Zone na DNS serveru bude pravilno konfigurisana, i da postoje odgovarajuci PTR zapisi za sve A zapise iz Forward Lookup Zone. Zona 127.in-addr.arpa se kreira po defaultu, i sa "poddomenom" 0 i "podpoddomenom" 0 i PTR zapisom 1, ona prevodi 127.0.0.1 u localhost, i mozes je videti ako u DNS konzoli kliknes na View > Advanced (treba bi takodje da vidis i zone 0.in-addr.arpa i 255.in-addr.arpa). Ako je tamo, onda tvoji klijenti ne vide tvoj DNS server kad dobijas onu gresku, a ako nije tamo, onda cu morati pitati cika Google-a sta kaze o tome...

[ gogi100 @ 22.06.2009. 08:31 ] @

Prvo u tcp/ip propreties na svakom klijentu stoji i adresa mog dns servera.
drugo kad kliknem u dns konzoli na dns server properties i jezicak forwarders u opciji dns domain stoji all other domains a u selected domain's forwarder ip address list stoji prazno.
trece u reverse lookup zones vidim 0.in-addr.arpa, 127.in-addr.arpa i takodje 255.in-addr.arpa i nista drugo. Sta bi tu trebalo dodati ili treba da tako stoji?

[ valjan @ 22.06.2009. 10:11 ] @

Ako tvoja mreza koristi npr. 192.168.0.X adresni opseg, onda bi trebao da imas i 0.168.192.in-addr.arpa zonu, gde je svaki PTR zapis u stvari onaj X iz 192.168.0.X. Znaci, ako nemas takvu zonu, klikni desnim dugmetom na Reverse Lookup Zones, odaberi New Zone, klikni Next, proveri da li je odabrano "Primary Zone" i stiklirano "Store the Zone in Active Directory" pa klikni Next, proveri da li je odabrano "To all DNS servers in the active directory domain..." pa klikni Next, unesi network ID tvoje mreze (zavisi od tvoje subnet maske, u onom gornjem promeru tu bi ukucao 192.168.0) pa klikni Next, odaberi "Allow only secure updates" i klinki Next, pa Finish.

U Forward Lookup Zoni proveri sve A zapise za tvoj domen, i vidi da li je stiklirano "Update associated pointer (PTR) record". Narocito obrati paznju da se i A i PTR zapisi za DC pojave u odgovarajucim zonama (iako je on ujedno i nameserver pa vec postoje NS zapisi za njega). Proveri vise puta tokom dana da li su jos tamo, jer ako je Aging/Scavenging opcija pogresno podesena, moze se desiti da zapis za DC bude obrisan (to se meni recimo desavalo u jednom domenu).

Takodje, proveri u Properties DHCP servera na kartici DNS da li su odabrane opcije "Enable DNS dynamic updates according to the settings below", "Dynamically update A and PTR records only if requested by DHCP client" i "Discard A and PTR records when lease is deleted", i proveri na kartici Advanced preko dugmeta Credentials da li se koristi ispravan nalog za automatsko azuriranje podataka na DNS serveru (odnosno da li taj user ima prava da azurira podatke na DNS serveru, i da li je password ispravan).

[ gogi100 @ 22.06.2009. 11:51 ] @

U Reverse Lookup zones nisam imao 0.168.192.in-addr.arpa zonu pa sam je postavio kako si mi rekao. Forward lookup zones postoje A zapisi sa cekiranim Update associated pointer (PTR) record. Tu sam primetio da mi se Host(A) zapisi u forward lookup zones za moj domen ne poklapaju sa brojem zapisa PTR(A) u Reverse Lookup Zones 0.168.192.in-addr.arpa zoni koju sam ubacio.
U propreties-u DHCP servera postoje stoji cekirano "Enable DNS dynamic updates according to the settings below", "Dynamically update A and PTR records only if requested by DHCP client" i "Discard A and PTR records when lease is deleted" a na kartici Advanced i u dugmetu Credentials username i domain stoji prazno, a pod password stoje zvezdice. Sta tu treba staviti da li administratorski user i naziv domaina ili treba da stoji ovako kako je postavljeno?

[ gogi100 @ 22.06.2009. 11:59 ] @

sada kad sam na klijent masini ubacio dobio sam opet isto
nslookup 127.0.0.1

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\xxxxx>nslookup 127.0.0.1
*** Can't find server name for address 192.168.0.x: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.0.x

Name:    localhost
Address:  127.0.0.1

[ valjan @ 22.06.2009. 13:00 ] @

Da li mozes da pingujes svoj DNS server koristeci njegovu IP adresu, NETBIOS ime i FQDN ime? Znaci, recimo da je DC (DNS) na IP 192.168.0.100, da se zove Glavni-Server i da je nadlezan za domen moj.domen. Da li mozes uspesno da odradis "ping 192.168.0.100", i "ping glavni-server", i "ping glavni-server.moj.domen"?

Da li ti je DHCP autorizovan za tvoj domen? Username koji treba da uneses pod Credentials bi trebao da bude onaj koji ima pravo citanja i pisanja na DNS serveru, a to mozes proveriti na DNS serveru na Security kartici u Properties za odgovarajucu Forward Lookup Zone. Uglavnom bi Domain Admin i Enterprise Admin trebali da imaju sva potrebna prava, pa mozes njih da iskoristis.

Sta imas pod 127.in-addr.arpa zonom?

E da, da li imas PTR zapis za DC? Ako ga nema kreiraj ga rucno (otvori 0.168.192.in-addr.arpa zonu, klikni desnim dugmetom misa negde u prazno u desnom prozoru, i odaberi "New Pointer (PTR)" pa kreiraj zapis).

[ gogi100 @ 22.06.2009. 13:43 ] @

sto se tice pingovanja radi i ping ip adrese i netbios imena i fqdn imena. dhcp je autorizovan. Pod 127.in-addr.arpa zonom imam 2 fajla: start of authority koji se odnosi na moj dns server i name server fajl. Takodje postoji i jedan folder zove se "0" i u njemu se nalazi fajl 1 pointer(PTR) localhost. U Reverse lookup zone u 0.168.192.in-addr.arpa zoni nisam imao PTR zapis za moj DC pa sam ga kreirao ( to je 4-ti broj ip adrese)

[ gogi100 @ 22.06.2009. 13:49 ] @

kad ukucam nslookup 127.0.0.1 dobijem

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\xxxx>nslookup 127.0.0.1
Server:  dobijem ime servera
Address:  192.168.0.x

Name:    localhost
Address:  127.0.0.1

Medjutim kad ukucam nslookup ipadresa klijenta ipadresa servera

Code:

C:\Documents and Settings\xxxx>nslookup 192.168.0.x 192.168.0.x
Server: dobije se ime servera
Address: 192.168.0.x

*** ime servera can't find 192.168.0.126: Non-existent domain

C:\Documents and Settings\xxxx>

gde je sad greska

[ gogi100 @ 22.06.2009. 13:51 ] @

problem sam resio ubacio sam ptr zapis i za ovu klijent masinu gde mi izbacuje gresku.
Medjutim, meni se poruke event id 7062 i 9999 i dalje pojavljuju u dns logu
Sta bi mozda trebalo jos proveriti?
Da slucajno nije problem to sto moj internet provider ima dns server? Ja dobijam internet od njega tako sto sam konekciju koja dolazi od njega zakacio na jednu mreznu ,a druga mi od tog kompjutera ide u lokalnu mrezu. Na tom racunaru mi se nalazi proxy koji pusta internet u moju mrezu.

[ valjan @ 22.06.2009. 14:19 ] @

Na tom proxyju podesi default gateway samo na konekciji prema provajderu, a prema lokalnoj mrezi ostavi prazno polje za default gateway. DNS na obe konekcije na proxyju podesi prema tvom dns serveru. Postoji velika mogucnost da bas on stvara zatvorenu petlju, tj. da salje upit prema DNS-u tvog provajdera koju on vraca tvom DNS serveru.

I kao sto rekoh, DNS provajdera ne sme nigde da se pojavljuje u tvojoj mrezi, osim na Forwarders kartici tvog DNS servera. Znaci, svaki upit koji ne spada u tvoj domen, tvoj DNS ce proslediti serverima sa spiska na Forwarders kartici, i samo on bi to trebao da radi, u protivnom javlja se zbrka kao sto je ti imas da nedostaju zapisi u nekoj od zona i sl.

[ gogi100 @ 22.06.2009. 14:38 ] @

Na kartici forwarders u opciji dns domain stoji all other domains a u selected domain's forwarder ip address list stoji prazno. Da li bih tu trebao da stavim ip adresu domain servra mog providera? Meni se nigde drugde ip adresa domain servera mog providera ne pojavljuje sem na konekciji proxy racunara odakle dolazi internet. Da li bih u prefered dns internet konekcije proxy racunara umesto ip adrese dns servera providera trebalo da stavim moju ip adresu dns servera?

[ valjan @ 22.06.2009. 14:44 ] @

Da, DNS serveri provajdera idu u selected domain's forwarder ip address list, a na proxyju, kao i na svim drugim klijentima svugde treba da stoji IP tvojih DNS servera.

[ gogi100 @ 23.06.2009. 06:23 ] @

Mala zabuna na kartici forwarders u properties mog dns servera u dns domain stoji 'all other DNS domains' kad kliknem new trazi se da unesem ime dns domain ja ne znam ime dns domain-a mog providera. Ja sam samo u 'selected domain's forwarder ip address list' kliknuo na new i uneo ip adresu dns servera mog providera. Da li sam pogodio. Kada na mreznoj kartici od koje dolazi internet u properties tcip/ip prefered dns umesto dns servera mog providera ukucao ip adresu mog dns servera internet ne radi. To sam uradio oanko kako si mi preporucio.
Da li sam odradio onako kako si rekao?
Sinoc mi se i dalje pojavljivala even id 7062 sa sledecom porukom

Code:
Event Type:    Warning
Event Source:    DNS
Event Category:    None
Event ID:    7062
Date:        23.6.2009
Time:        1:48:21
User:        N/A
Computer:    server kompjuter
Description:
The DNS server encountered a packet addressed to itself on IP address mog novog servera. The packet is for the DNS name "ime starog servera". The packet will be discarded. This condition 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.
  5) Root hints.

Example of self-delegation:
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
  (bar.example.microsoft.com NS dns1.example.microsoft.com)
  -> BUT the bar.example.microsoft.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.

You can use the DNS server debug logging facility to track down the cause of this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 50 25 00 00               P%..

takodje mi se pojavljuje ova poruka koja umesto na ime mog starog servera The packet is for the DNS name "ime starog servera" upucuje i na ".",
kao da i dalje upucuje na stari server

_{[Ovu poruku je menjao gogi100 dana 23.06.2009. u 07:34 GMT+1]}

[ valjan @ 23.06.2009. 08:16 ] @

Proveri da li u Forward Lookup Zones imas zonu "." (tacka) i ako je imas obrisi je - to je tzv. "root" zona i to je recimo jedan od nacina da blokiras pristup Internetu (sto ti ne zelis).

Sto se tice greske 7062, pogledaj http://support.microsoft.com/kb/235689 i http://support.microsoft.com/kb/218814 i mozda ti nesto sa tih stranice pomogne.

[ valjan @ 23.06.2009. 08:25 ] @

Sad sam se setio necega - otvori Properties za tvoj domen u Forwards Lookup Zones, i pogledaj sta stoji na Zone Transfers kartici, i sta imas u prozoru koji dobijes kad kliknes na Notify dugme u donjem desnom cosku na Zone Transfers kartici. Ako na bilo kom od ova dva mesta imas unet tvoj trenutni DNS server, ili bilo koji server koji se ne koristi kao DNS, brisi ih odatle.

[ gogi100 @ 23.06.2009. 09:31 ] @

U Forward Lookup Zones postoji _msdcs.mojserver i mojserver. Tacke nema. U Transfer zones kartici nema nista sve je prazno i notify dugme je onemoguceno. Jedino sto sam primetio sto je mozda sumljivo u Root hints kartici postoji moj name sever sa ip adresom. Da li tu treba da postoji?
Takodje sam primetio da mi prilikom izbacivanja poruke event id 7062 sada umesto mog bivseg servera izbacuje naziv sajta koji posecuju korisnici sa lokalne mreze

Code:

Event Type:    Warning
Event Source:    DNS
Event Category:    None
Event ID:    7062
Date:        23.6.2009
Time:        1:48:21
User:        N/A
Computer:    server kompjuter
Description:
The DNS server encountered a packet addressed to itself on IP address mog novog servera. The packet is for the DNS name "ime sajta koji korisnik posecuje". The packet will be discarded. This condition 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.
  5) Root hints.

Example of self-delegation:
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
  (bar.example.microsoft.com NS dns1.example.microsoft.com)
  -> BUT the bar.example.microsoft.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.

You can use the DNS server debug logging facility to track down the cause of this problem.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 50 25 00 00               P%..

_{[Ovu poruku je menjao gogi100 dana 23.06.2009. u 10:45 GMT+1]}

[ valjan @ 23.06.2009. 10:33 ] @

U root hints treba da stoje samo root hints serveri (imena su im a.root-servers.net, b.root-servers.net, c.root-servers.net itd do m). DNS funkcionise tako da kad neki DNS server ne moze da pronadje zapis za neki racunar na nekom domenu, i ne dobija odgovor od forwarders servera, onda pita root hint servere za putanju do odgovarajuceg DNS-a. Recimo da radis upit za www.microsoft.com, root hint server bi uputio tvoj DNS na onog ko je nadlezan za com domen, taj bi ga opet uputio na onog ko je nadlezan za microsoft.com domen, i tamo bi dobio odgovor na kojoj Ip adresi se nalazi DNS server.

Posto je i tvoj server na tom spisku, taman imas lepo zatvorenu petlju: tvoj server pita samog sebe i zato ti se javlja ta greska. Znaci, obrisi ga odatle. Zbog toga mozda ni nisi imao pristup Internetu kada si promenio DNS podesavanja na proxyju.

[ gogi100 @ 23.06.2009. 11:04 ] @

da li u root hints mogu da stavim ip adresu dns server providera? opet kad sam obrisao u root hints ip adresu mog servera i u proxiju na konekciji koja ide za internet u prefered dns kad sam stavio ip adresu mog dns servera internet ne radi

[ valjan @ 23.06.2009. 11:15 ] @

Ne, root hints su specijalizovani serveri, i nemoj tamo nista da upisujes osim bas root hints servera. DNS serveri tvog provajdera mogu ici samo u Forwarders. A sto se proxyja tice, izgleda da nisam najjasnije objasnio ili ti nisi pazljivo citao - podesi konekcije onako kako su bile (znaci tvoj DNS na LAN konekciji, provajderov DNS na WAN konekciji), samo obrati paznju na DNS kartici na Advanced podesavanjima kom domenu se prijavljuje koja od tih konekcija, i ispravi ako je pogresna (LAN konekcija treba da se prijavi na tvoj domen, tj. tvoj DNS server, a WAN konekcija na domen tvog provajdera, tj. njegov DNS server - nemoj ih nikad mesati).

[ gogi100 @ 23.06.2009. 13:38 ] @

na kartici koja proxy kompjuter povezuje sa mrezom u properties tcp/ip u advanced stoji ip adresa mog dns servera. To je znaci ok. Izbrisao sam u root hints moj dns server. Sad cu pratiti da vidim sta se desava u dns logu

[ gogi100 @ 24.06.2009. 06:49 ] @

profunkcionisalo je nema vise gresaka event id 7062 i 9999

[ gogi100 @ 03.07.2009. 13:54 ] @

danas mi se kad sam restartovao server u event vieweru pojavilae greske

Code:
Event Type:    Warning
Event Source:    DNS
Event Category:    None
Event ID:    4515
Date:        3.7.2009
Time:        14:45:54
User:        N/A
Computer:    server
Description:
The zone mojdomen was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.mojdomen. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.

If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.

If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.

To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00               ?%..

Event Type:    Error
Event Source:    DNS
Event Category:    None
Event ID:    4004
Date:        3.7.2009
Time:        14:42:14
User:        N/A
Computer:    server
Description:
The DNS server was unable to complete directory service enumeration of zone moj domen.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00               *#..

Sad izgleda da dns ne saradjuje sa active directory. U cemu je sad problem?

[ valjan @ 03.07.2009. 14:54 ] @

Event ID 4004 se cesto javlja u domenima koji imaju samo jedan server koji je ujedno i DC i DNS i igra jos neku ulogu (web server, mail server, DB server,...). Prilikom bootovanja NetLogon pokusava da se registruje u odgovarajucu DNS zonu, ali zbog sporog servera ili zbog velikog broja servisa koji se pokrecu AD jos nije u potpunosti spreman za rad i eto tebi greske. Znaci tu mozes slobodno da ignorises, a ako nekad budes imao i drugi DNS server, onda je preporuka da u TCP/IP properties stavis onaj drugi kao primarni (znaci na DNS1 postavis DNS2 kao primarni, a na DNS2 to treba da bude DNS1).

Sa drugim event ID-jem se jos nisam susretao, pitacu cika Googla pa ti javim sta sam saznao.

[ gogi100 @ 03.07.2009. 18:19 ] @

na netu sam nasao sledece objasnjenje za event id 4515

Code:
. If you receive event ID 4515 and also have difficulty changing the Active Directory (AD) replication scope from all domain controllers (DCs) to just DCs that host the DNS service, perform these steps to resolve the problem:

   1. Start the Microsoft Management Console (MMC) DNS snap-in (Start, Programs, Administrative Tools, DNS).
   2. Stop DNS services on all but one DNS server. (Right-click the DNS server name and select Stop from the All Tasks context menu).
   3. On the remaining DNS server, turn off AD integration for the zones that are experiencing the problem. To do so, right-click the zone and select Properties. Click Change under "Type of DNS" and clear the "Store the zone in Active Directory" check box.
   4. Restart the DNS service on the server. (Right-click the DNS server name and select Restart from the All Tasks context menu.)
   5. Reenable AD integration on the zone and force replication to other DCs.
   6. Start the DNS service on the other DNS servers by right-clicking the DNS server name and selecting Start from the All Tasks context menu.

You should no longer see event ID 4515 in the log.

Nije mi jasno ja samo imam jedan dns server,a ovde se pominje vise koji moraju biti stopirani. Da li ja moram da stopiram moj dns server? Da li se ovaj slucaj odnosi kada u mrezi postoji vise servera?

[ valjan @ 04.07.2009. 08:53 ] @

Mislim da je uputstvo sa http://support.microsoft.com/kb/867464 mnogo adekvatnije za tvoj slucaj. Ali sam naisao i na sledece:

Citat:

In a Windows Server 2003 domain, changing the replication scope using the DNS snap-in can cause this error. It may only happen once, but if it repeats, the old copy might not have been deleted. When this happens, use ADSI Edit from the Windows Support Tools to delete the duplicate. To get to the necessary partition, such as DomainDNSZones, you must tell ADSI to use a custom connection point of DC=DomainDNSZones, DC=domain, DC=com. You cannot see this partition using any of the default well-known naming contexts.

U svakom slucaju, ako se ta greska javi vise puta, idi na onaj MS Support link, pokreni ADSI edit pa isprati uputstva, a do tada ga samo prati kako se ponasa. Mada, mzoes probati i to sto si ti nasao, samo preskoci korake 2 i 6, posto imas samo jedan DNS server u tvom domenu.

[ gogi100 @ 06.07.2009. 06:20 ] @

pratio sam za vikend i nisam naisao na gresku event id 4515 niti event id 4004. Izgleda da se ovo trenutno desilo. Praticu jos neki dan