Home › Forums › OS X Server and Client Discussion › DNS › BIND not resolving quries after restart on 10.3 Server

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 15, 2004 at 8:09 am #359161
    cmcfarling
    Participant

    Everytime I reboot my XServe G5 running OS X Server 10.3.5, the DNS server wil not resolve queries until the service is stopped and started.

    Immediately after a reboot, if I attempt to resolve a DNS name from a client machine using NetworkUtility, the query times out. Not until I restart the DNS server service are quries resolved properly.

    This system has been completely wiped and reinstalled twice. Also, the forward and reverse zones have been deleted and recreated a multiple times. So, I don’t think this is a “corrupt” zone file, something else is going on.

    As an undesireable side effect, The Kerberos KDC server (required for single-singon) fails to start up after a system reboot due to the DNS server not working properly. This requires additional steps to get the KDC running after restarting the DNS service, which is a pain.

    Has anyone experienced similar behavior or does anyone have any suggestions as to what might be happening here?

    Thanks for any input.

    CM

    October 30, 2004 at 3:36 pm #359753
    Detrius
    Participant

    I have also had this exact same problem. One of the servers is on a wireless network, and so I assumed this was due to the fact that the wireless network is not up and running. However, the second server (configured yesterday for the first time) is on a gigabit connection and is doing the same thing.

    In addition, one of these servers consistently fails DNS lookups the FIRST time around. From that point on, it responds correctly for that DNS entry–I suspect within the TTL.

    I am starting to believe this is a 10.3.5 bug, as I did not have these problems with 10.3.4.

    November 1, 2004 at 1:53 am #359762
    Detrius
    Participant

    As noted in another thread, updating to BIND 9.3 fixes the non-cached resolution failures. However, this did not fix my issues with the DNS server needing to be restarted after a reboot.

    I’ve tweaked my tcsh login scripts to restart the necessary daemons as a slightly easier workaround.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed

Copyright © 2025 AFP548. All Rights Reserved.