DNS Service doesn't start on bootup

Discussion in 'DNS Server' started by Joe Blizzard, Dec 16, 2009.

  1. Joe Blizzard

    Joe Blizzard Guest

    Fresh install of 2008 R2, DNS and AD DS roles installed. On reboot, DNS
    doesn't start automatically, but I can log on and start DNS manually. In
    system events, I see ID 7036 "The DNS Server service entered the stopped
    state," followed by ID 7023, "The DNS Server service terminated with the
    following error: The network is not present or not started." Suggestions on
    where to start?
     
    Joe Blizzard, Dec 16, 2009
    #1
    1. Advertisements


  2. As Jonathan indicated, it appears that the message you are getting, "...The
    network is not present or not started," may indicate that the NIC or network
    services are not starting first, which is required for DNS and other network
    based services. The 7036 and 7023 eventID#s are generic to any services.
    We'll need something a little more specific. Do you see any other error
    messages in any other event logs?

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Please reply back to the newsgroup or forum for collaboration benefit among
    responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
    2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer

    For urgent issues, please contact Microsoft PSS directly. Please check
    http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [MCT], Dec 17, 2009
    #2
    1. Advertisements

  3. Joe Blizzard

    Joe Blizzard Guest

    I see some warnings from the network adapter as the link goes down and back
    up on each port before initializing. This happens prior to other services
    starting. It's an Intel PRO/1000 PT dual port server adapter configured for
    teaming. I tried disabling teaming, but DNS still failed to auto-start.
     
    Joe Blizzard, Dec 17, 2009
    #3

  4. Have you checked and tried to eliminate the simple things, such as a bad
    wire, connection loose, bad switch port, etc?

    Ace
     
    Ace Fekay [MCT], Dec 18, 2009
    #4
  5. Joe Blizzard

    Joe Blizzard Guest

    Startup messages from other services appear in the event logs after the
    successful NIC initialization message.
     
    Joe Blizzard, Dec 20, 2009
    #5
  6. Joe Blizzard

    Joe Blizzard Guest

    I've tried different cables and different switch ports. I changed some NIC
    parameters (specified link speed instead of autonegotiate for the individual
    NICs and disabled 'probes' for the team) and this eliminated all of the NIC
    error events, but DNS still doesn't auto start.
     
    Joe Blizzard, Dec 20, 2009
    #6

  7. How about drivers? Have you considered disabling the team and see if that is
    causing it.

    Apparently something is holding it up. It's difficult to ascertain.

    Ace.
     
    Ace Fekay [MCT], Dec 20, 2009
    #7
  8. Joe Blizzard

    Joe Blizzard Guest

    Disabling teaming didn't help. However, I just disabled the Intel NIC and
    installed an old Broadcom NIC and DNS started on reboot, just like it's
    supposed to. It appears there's something wonky with my Intel NIC or its
    drivers. Armed with that information, I think I'll continue troubleshooting
    tomorrow, on company time.
     
    Joe Blizzard, Dec 20, 2009
    #8

  9. That's good to hear you narrowed it down. Let us know how you make out.

    Ace
     
    Ace Fekay [MCT], Dec 21, 2009
    #9
  10. Joe Blizzard

    Joe Blizzard Guest

    This morning I uninstalled the Intel drivers and started over. With the
    Microsoft driver, each NIC in the PRO/1000 PT Dual adapter works fine as a
    standalone NIC. I can load the Intel drivers and I'm still good in
    standalone, but if I team the NICs, DNS fails to start. Then if I remove the
    team and try to return to standalone, DNS fails on a standalone NIC. The
    only way I've been able to get it back to working is to uninstall the Intel
    drivers and start over again. I've repeated this cycle a couple of times.
    Intel support hasn't been any help so far.
     
    Joe Blizzard, Dec 22, 2009
    #10

  11. Dumb question. What kind of switch do you have? Maybe it's not recognizing
    the team properly if both interfaces are plugged into the same port?

    Ace
     
    Ace Fekay [MCT], Dec 23, 2009
    #11
  12. Joe Blizzard

    Joe Blizzard Guest

    Dell 5324. I have an identical NIC in an Exchange server on the same switch
    with no problems. No DNS role on that one, though.
     
    Joe Blizzard, Dec 23, 2009
    #12

  13. Maybe there's a delay on the switch side that is causing DNS to hang? Can
    you check the port settings?

    Ace
     
    Ace Fekay [MCT], Dec 23, 2009
    #13
  14. Joe Blizzard

    Joe Blizzard Guest

    I can, but I don't know what I should be looking for there. (Right now I'm
    trying to get Intel to fix a broken download link so I can try a driver
    update.)
     
    Joe Blizzard, Dec 23, 2009
    #14
  15. Sorry, I can't remember the setting. It's regards tuning the teaming config.
    Here's Cisco's take on it for their Catalyst series.

    http://www.cisco.com/en/US/products...s_tech_note09186a00800a7af0.shtml#nic_teaming

    Ace
     
    Ace Fekay [MCT], Dec 25, 2009
    #15

  16. Jonathan,

    The MSKB you posted, http://support.microsoft.com/kb/954423, indicates the
    following:

    - The server does not have network connectivity.
    - The network device to which the server is connected takes a longer time to
    start than the server.

    Therefore, that was why I was pointing to switch configuration. Cisco claims
    there is an issue with their Catalyst where the spanning tree algorithm
    hangs and may intermittently drop connection while it recycles the port. I
    don't know about the Intel switch Joe has, but it alerts me that the issue
    *may* reside with the switch.

    Ace
     
    Ace Fekay [MCT], Dec 25, 2009
    #16
  17. JdeBP> You're going off at tangents somewhat.  The basic etiology
    Regarind a registry tweak, are you saying to make DNS dependent on the
    network services to start first?

    Ace

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Please reply back to the newsgroup or forum for collaboration benefit
    among responding engineers, and to help others benefit from your
    resolution.

    Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
    MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer

    For urgent issues, please contact Microsoft PSS directly. Please check
    http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [MCT], Dec 26, 2009
    #17

  18. Then let's see how Joe responds to your questions before moving forward on
    any other assumptions.

    Ace
     
    Ace Fekay [MCT], Dec 26, 2009
    #18
  19. Joe Blizzard

    Joe Blizzard Guest

    Updating the Intel NIC driver resolved the problem. I reproduced the issue
    on a second machine with exactly the same results. With version 14.7 of the
    driver, DNS fails at startup. With driver version 14.8.3, DNS starts as it
    should. Apparently something in the newer driver corrects the problem of the
    network not initializing to the DNS service's satisfaction at startup when
    NICs are teamed.
     
    Joe Blizzard, Jan 4, 2010
    #19

  20. Good find. Glad you figured it out. So it may be related to the switch ports
    the way the driver handles the traffic.

    Cool! Cheers!

    Ace
     
    Ace Fekay [MCT], Jan 4, 2010
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.