DNS server opsætning

Jeg vil tro jeg skal sætte den op som "slave" men da jeg jo hedder .local kender ISP's NS jo ikke noget til det....

skal jeg istedet sætte det til .dk (der er en NS record for srv_01.sophiehaven.dk hos isp)

Den fejl jeg får i DNS event loggen er:
The DNS server encountered error 32 attempting to load zone drabant-it.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.

Og jeg får denne fejl i min application log:
Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.

teamdev: går ud fra du har en anden dns server. Sæt den til at være primær dns server i din netværksopsætning. Forsøg at replikere zonen. Sæt derefter serveren selv som primær og den anden server som sekundær.

Test. evt. zoneoverførsel med nslookup og så skriv ls -a sophiehaven.local

Hej riversen.

Hvis det bare var så nemt :-)

Nej jeg har nemlig ikke en anden dns server. Det er en helt ny opsætning, ny server nyt domæne.

kom lige med id'er og source i eventvieweren

Der er en eventid i DNS eventen 6702 med følgende indhold:
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.

-----------------

Der står jo at den umiddelbart kan ignoreres.......

I application eventloggen er en eventid 1054 med dette indhold:

Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


den gentager sig hvert 5. minut

så mangler du bare at poste sourcen også.

Eventid 1054 er usernv
og eventid er DNS

har endnu en:
eventid 4521  source DNS

The DNS server encountered error 32 attempting to load zone drabant-it.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Der skulle selvfølgelig stå:

Eventid 1054 er usernv
og eventid er DNS

har endnu en:
eventid 4521  source DNS

The DNS server encountered error 32 attempting to load zone sophiehaven.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

prøv at skrive "dnscmd /config /bootmethod" på dns serveren og se om det hjælper på 4521 fejlen.

Det prøver jeg så.

Tror en del af de andre fejl er løst med en reinstallation, så den har en frisk dns.
Har dog stadig et par Eventid 1054 er usernv og source er DNS

Vi ser lige på det.

vedr. 1054 så se her: http://www.eventid.net/display.asp?eventid=1054&eventno=1393&source=Userenv&phase=1

Hmmm det jeg udleder er at det er NIC driveren der hikker?

mener også andet var nævnt, men det var i hvert fald en genganger, så måske.

Hej riversen. Ja det var forsøget værd. Men hjalp ikke at opdatere driveren til NIC.

Jeg fik fortsat en 1054
Til gengæld faldt jeg over en kommentar med en der havde installeret opdaret driver til sin AMD

----- indsat herunder ------

AceyMan (Last update 2/3/2007):
We have a new Opteron server (1210, AM2 socket) on a Tyan S3950 mainboard (Broadcomm HT-1000 chipset).  This server was promoted to a DC and now holds all the FSMO roles. We began to see this event every 5 minutes continuously whether a user was logged on or not. DNS and Ethernet tweaks did not help. I found a blog entry that said to install the "AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003". After installing this driver and rebooting, the 1054 events are gone.

-------- slut -------

Det tænkte jeg jo også var forsøget værd eftersom min server også er med AMD processor

Jeg hentede så drivere her:
http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html

og i skrivende stund er der intet grimt i Application loggen. (eller i andre logs)

Så smid et svar riversen så får du points. Det var jo dig der bragte mig på sporet og tak for det

ja, det var den jeg tænkte på i min forrige kommentar. Behold bare point.

Jamen så siger jeg da tak for hjælpen.

Mine eventlogs er uden alerts bortset fra et par stykker i system der klager over nogle manglende printerdrivere, det sker når jeg logger på via remote.
Så det er små ligegyldigheder :-)

Riversen:

Har endnu en eventlog ting.
http://www.eksperten.dk/spm/840253