DNS Server (2008) failing until root hints updated

Discussion in 'DNS Server' started by GregSteer, Oct 29, 2008.

  1. GregSteer

    GregSteer Guest


    I've got a new (about 1 month) server 2008 box out at a clients and
    periodically it stops serving DNS requests. Restarting the DNS Server service
    has no effect but running a manual "copy from server" in the root hints tab
    of the DNS server resovles the issue.

    There are no enlightening events in the logs to shed any light. Has anyone
    else experienced this phenomenom at all? It's the first live 2008 server I've
    deployed and if this is a known problem then I could do with having the
    resolution clear to avoid/solve in the future.

    IPV6 is enabled as Exchange 2007 is installed, it grumbled about it not
    being available, and it is the IPv6 addresses that appear next to the IPV4
    addresses when the "copy from server" button is hit.


    GregSteer, Oct 29, 2008
    1. Advertisements

  2. Hello GregSteer,

    If you don't use IPv6 you can uncheck it on the NIC properties. What exactly
    do you mean with "periodically it stops serving DNS requests"? What are the
    error message or symptoms on the clients?

    Best regards

    Meinolf Weber
    Meinolf Weber, Oct 29, 2008
    1. Advertisements

  3. GregSteer

    GregSteer Guest

    Hi Meinolf,

    The times vary, so far its happened 3 times since installation with gaps of
    7, 5 and 10 days. The clients simply start failing to receive DNS responses,
    ie they are unable to reach the internet, although internal routing appears
    to be working ok.

    A quick "copy from server" in the root hints fixes it which is the oddest

    Nothing is using ipv6 as far as I am aware although I'm hesitant to disable
    it as Exchange 2007 insisted on it being enable during installation.


    GregSteer, Oct 30, 2008
  4. Hello GregSteer,

    Have you configured the Forwarders on the DNS server properties in the DNS
    management console or do you use your ISP's DNS ip on the NIC's?

    Best regards

    Meinolf Weber
    Meinolf Weber, Oct 30, 2008
  5. GregSteer

    GregSteer Guest

    Hi Meinholf,

    No forwarders are set, settings on local NIC point to the server itself for

    <<< SNIP >>>
    GregSteer, Oct 30, 2008
  6. GregSteer

    GregSteer Guest

    As an additional I do know that I can put the forwarders in and it would
    probably solve the issue, but I've got plenty of 2000/2003 boxes out there in
    this setup that have worked fine from day 1 and are still working, it's odd
    that the first 2008 server where IPv6 is install is having issues.


    << SNIP >>
    GregSteer, Oct 30, 2008
  7. GregSteer

    Curt L. Guest

    I have what might be a similar situation, so I am posting to this thread
    because it may be a related issue. I too, have a relatively new 2008 box
    with Exchange 2007 that stops (times out) on DNS request. Outlook 2007 on
    the client PC seems to be the leading indicator as program goes into
    “disconnect†mode. I have DNS forwarders set on this single homed server.
    The DHCP service passes itself as the primary DNS and the ISP’s DNS as the
    secondary – so internet browsing is not affected. So, when I restart the DNS
    service on the server, the PC still do not resolve DNS. It is not until I
    restart the DNS client on the server that the PC is able to resolve DNS
    requests to the server. This fix is almost instantaneous and does not
    require the copy mentioned in this thread. This service restart is not a
    good long term solution. The server logs do not report any DNS issues and
    the services are listed as “started†before I bounce them.

    I hate to trample on the original poster’s question, but have you tried
    restarting the DNS services on the server? If so, we might have the same

    - Curt
    Curt L., Nov 3, 2008
  8. GregSteer

    GregSteer Guest

    Hi Curt,

    Thanks for the response - I've been away so only just read it. It does sound
    like you have exactly the same issue as myself, I have tried restarting the
    DNS Server Service which did not resolve anything but did not actually try
    restarting the DNS Client Service on the server, next time the company in
    question calls to let us know of the problem I'll test this.


    GregSteer, Nov 11, 2008
  9. GregSteer

    Curt L. Guest


    For us, it has been over a week since the last reported DNS incident. We
    all know how difficult it is to diagnose these (seemingly) random issues.
    Although it is counterintuitive to restart the DNS client on the server in
    this situation, this was my experience. Perhaps you will have a different


    - Curt
    Curt L., Nov 11, 2008
    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.