dns server reboots, everyone reboots?

Discussion in 'DNS Server' started by Michael Roper, May 28, 2005.

  1. I have a small home network with four to six boxes, one of which is the
    sole DC and DNS server (2k3). Occasionally this machine is rebooted,
    and every time it is, all the others on the network lose DNS--no one can
    see anyone. The only way I've found solve it is rebooting all the other
    boxes. Is this normal?

    Michael Roper
    Michael Roper, May 28, 2005
    1. Advertisements

  2. In
    Yes it is normal if you only have one DC. The DC will be the master browser
    for Network places, it should be the only DNS server, and it authenticates
    all domain accounts. It is highly recommended that if yhr DC needs to be
    rebooted during business hours, you should have two DCs. In fact you should
    have a minimum of two DCs anyway, even if you keep daily backups. The DC
    maintains and authenticates all user and computer accounts, if you lose the
    DC, you see the consequences. Imagine having to build a new DC or restore
    before anyone can do anything.

    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    Keep a back up of your OE settings and folders
    with OEBackup:
    Kevin D. Goodknecht Sr. [MVP], May 29, 2005
    1. Advertisements

  3. Assuming, based on your symptoms, that the other machines on the network
    are resolving against the 2K3 box, try restarting the "DNS Client"
    service (DNSCACHE).
    Dean Wells [MVP], May 29, 2005
  4. Michael Roper

    Herb Martin Guest

    No, but it isn't uncommon if your CLIENT NIC DNS settings
    are misconfigured to include the ISP DNS or other external DNS
    servers instead of STRICTLY the internal DNS server(s).

    All internal clients must use strictly your INTERNAL DNS
    server (set) -- DCs, the DNS server, and other servers are
    DNS clients too!

    Many people think (incorrectly) that clients will use one DNS
    server then try the next one -- it even works by accident on an
    intermittent basis.

    What really happens is that a client uses the information given
    by the FIRST DNS server that answers and when one goes down
    it will try the second -- problem is that then it latches onto the
    other DNS server (set) which is usually for external names and
    therefore it cannot resolve anything internally.

    Worse, it may not even switch back right away when the original
    (preferred) DNS server comes back on line.

    Kevin & Dean (other posts) have good posts: you really do need
    two DCs if you reboot during "working hours" and you may be
    caching the "wrong" answers too.

    But the caching of "not found" is only five minutes and so the
    cache should reset fairly quick after a DC reboot, as should the
    nameserver for both DNS and NetBIOS when the DC returns.

    In fact, broadcasts and NetBIOS resolution may actually allow
    some things to work while the DNS is down, or even (badly)
    after it returns. All of this "help" actually makes the problem
    harder to define and troubleshoot.

    The key is usually preventing the clients from latching onto an
    external DNS server.

    DNS for AD
    1) Dynamic for the zone supporting AD
    2) All internal DNS clients NIC\IP properties must specify SOLELY
    that internal, dynamic DNS server (set.)
    3) DCs and even DNS servers are DNS clients too -- see #2
    4) If you have more than one Domain, every DNS server must
    be able to resolve ALL domains (either directly or indirectly)

    netdiag /fix

    ....or maybe:

    dcdiag /fix

    (Win2003 can do this from Support tools):
    nltest /dsregdns /server:DC-ServerNameGoesHere

    Ensure that DNS zones/domains are fully replicated to all DNS
    servers for that (internal) zone/domain.

    Also useful may be running DCDiag on each DC, sending the
    output to a text file, and searching for FAIL, ERROR, WARN.

    Single Label domain zone names are a problem Google:
    [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
    Herb Martin, May 30, 2005
    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.