locked
event id 4013 RRS feed

  • Întrebare

  • The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

    Am si eu o problema cu acest warning in DNS. De fiecare data cand dau restart la server sau ma rog dupa ce si-a facut un update si se restarteaza, in DNS log apare acest warning. Pana recent foloseam acel loopback 127.0.0.1 si credeam ca aceasta ar fi problema, dar am schimbat cu ip-ul local am restartat serverul si tot imi apare acest warning

    Scuze sunt incepator, si cam greu cu exprimarea in termeni clari, sper sa fi fost clar cat de cat

    Multumesc foarte mult, orice ajutor ar fi de apreciat


    willockss

    vineri, 8 iunie 2012 12:32

Răspunsuri

  • Salut,

    Exchange-ul depinde foarte mult de Global Catalog si foarte probabil serverul tau de exchange este si controlor de domeniu, deci si DNS (desi nu e o regula).

    Faptul ca are adresa de loopback ca DNS primar inseamna ca se uita prima data catre el insusi pentru rezolvarea de nume (fiind si server DNS).

    De ce nu apare si pe exchange?

    Probabil versiuni diferite de windows server....Poate pe exchange ai 2003?

    Ce versiune de Windows server are Domain controller-ul instalat recent?

    Conform BPA din Windows Server 2008 R2 pentru DNS (http://technet.microsoft.com/en-us/library/ff807362(ws.10).aspx)

    If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.


    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/


    marți, 10 iulie 2012 13:25

Toate mesajele

  • Salut,

    Incearca comanda dcdiag /test:dns si verifica atent daca ai ceva erori. Incearca si repadmin /syncall , repadmin /showrepl , repadmin /replsummary si verifica de erori de replicare.

    Posteaza aici daca apare ceva cu "failed".


    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/

    vineri, 8 iunie 2012 17:12
  • aici mi-a dat erori la comanda repadmin /replsummary

    C:\Users\Administrator>repadmin /replsummary
    Replication Summary Start Time: 2012-06-08 22:27:17

    Beginning data collection for replication summary, this may take awhile:
      ....


    Source DSA          largest delta    fails/total %%   error


    Destination DSA     largest delta    fails/total %%   error


    willockss

    vineri, 8 iunie 2012 20:30
  • Aici apare ca nu ai replicari. Nu cumva ai doar un domain controller?

    Dupa enuntul warningului apare ceva de genul:

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: <%status code%>

    ce scrie la status code?

    Daca ai sistem 2008 r2 ai in server manager la rolul DNS,  un best practices analyzer. Ruleaza-l si vezi ce spune.

    Posteaza outputul pentru nslookup. Incearca si dcdiag /fix si netdiag /fix.

    Restarteaza serviciul netlogon.


    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/

    vineri, 8 iunie 2012 20:57
  • The network adapter Local Area Connection does not list the loopback IP address as a DNS server, or it is configured as the first entry.

    Asta e eroarea pe care mi-o da cand am rulat best practice analyzer si wrning

    Local Area Connection has only the preferred DNS server configured.

    There is only one forwarder configured on the DNS server(more then one forwarder should be configured)

    Da si am un singur Dc


    willockss

    vineri, 8 iunie 2012 22:00

  • C:\Users\Administrator>nslookup
    Default Server:  UnKnown
    Address:  192.168.67.2

    willockss


    • Editat de willockss vineri, 8 iunie 2012 22:02
    vineri, 8 iunie 2012 22:01
  • Trebuie sa creezi un reverse lookup zone in dns si sa creezi o inregistrare PTR . Detalii aici. Se pare ca ar trebui sa pui adresa de loopback (127.0.0.1) ca si server DNS secundar in proprietatile TCP/IP desi nu am vazut pe nimeni sa foloseasca adresa de loopback pentru rezolvare de nume. Oricum daca vrei mai multe detalii urmeaza pasii de aici si zi-mi daca mai apar acele warning-uri.

    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/

    marți, 12 iunie 2012 11:41
  • Am incercat toate combinatiile posibile, din ce mi-ai relatat si la fel, tot apare acel warning cand dau restart. Dar un lucru foarte ciudat spre exemplu.

    Am 2 servere. Unu este doar pentru websiteuri, si celalalt e doar pentru exchange.

    Acel server de Exchange, are ca DNS primar adresa de loopback, si cand ii dau restart nu are acel warning. De ce?

    Adica nici nu stiu daca ar trebui sa am in serverul de exchange adresa de loopback ca DNS primar? 

    Sunt confuz, numai inteleg nimic :(


    willockss

    miercuri, 13 iunie 2012 06:54
  • Salut,

    Exchange-ul depinde foarte mult de Global Catalog si foarte probabil serverul tau de exchange este si controlor de domeniu, deci si DNS (desi nu e o regula).

    Faptul ca are adresa de loopback ca DNS primar inseamna ca se uita prima data catre el insusi pentru rezolvarea de nume (fiind si server DNS).

    De ce nu apare si pe exchange?

    Probabil versiuni diferite de windows server....Poate pe exchange ai 2003?

    Ce versiune de Windows server are Domain controller-ul instalat recent?

    Conform BPA din Windows Server 2008 R2 pentru DNS (http://technet.microsoft.com/en-us/library/ff807362(ws.10).aspx)

    If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.


    MCTS - Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. http://mariusene.wordpress.com/


    marți, 10 iulie 2012 13:25