Re: Server slow bootup, DNS not working when server looks to itself for DNS resolution

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Yes but the SAD1 server will hang if it does, I have to point it to the
other server and after reboot point it back to itself.

steve wrote:

"jimbo" <jridout@xxxxxxxxxxxxx> wrote in message
news:1161861414.136078.22960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The other DC server at was paired with it has been replaced. There were
no errors during this work. I don't think its related as the other
server is sharing the same DNS info. After boot up when the affected
server is pointed back to itself for DNS, all is well.

spoofer wrote:
So did you or anyone else change anything before this reboot ?

Regards
<jridout@xxxxxxxxxxxxx> wrote in message
news:1161859351.800989.275460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all, got two servers, SAD1 and SAD2, both DCs in a large AD. SAD1
does all the "roles" and GC, SAD2 is a new server which replaced an
older server which done all the roles. These were moved to SAD1, etc...
All fine.

Both servers have been running 100%, however yesterday I done a reboot
of SAD1 and it took ages to load up to the login screen, I even had an
alert to say DNS had'nt loaded, it does but takes ages.

When I log in, you can't surf, the server can't find its name, GP fails
etc... If I point the DNS of the NIC to the other SAD2 server
"additional" DC, it all springs into life 100%. If I reboot again its
perfect, if I try and change the IP back it still works fine, it seems
to happen during/after boot up.

I have tried clearing DNS cache, restoring the dns folder in system32.
The only thing I can think off is uninstalling and reloading DNS.
However although the zones rep with SAD2, I don't want to risk losing
the forward and reverse zones.


Any suggestions?? I feel DNS is having problems starting up, the data
in those zones seems ok.


Thanks.


Am I right in thinking that when you have two DC/DNS machines, you should
(on each machine) point the primary DNS server to it's peer and secondary to
itself? I seem to remember reading that on this NG a fair while ago ..?

steve

.



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)