Delegation Requires a Stop and Restart of the DNS Server

Last reviewed: August 13, 1997
Article ID: Q154556
The information in this article applies to:
  • Microsoft Windows NT Server versions 4.0

SUMMARY

Depending on the steps you take to delegate a subzone to a different server by means of Domain Name System (DNS) Manager, you may or may not be required to stop and restart the DNS service.

MORE INFORMATION

If you follow these steps, you will not need to restart the DNS server service:

  1. In DNS Manager, select the zone and right click.

  2. Select New Domain and type the name of the subzone to be delegated. (For example, for zone nc.ms.com, subzone proto.)

  3. Select the newly created subzone and right-click.

  4. Select Add New HOST, and enter the name and IP address of the DNS server to which the subzone will be delegated.

  5. Select the new subzone and right click.

  6. Select Add New Record/NS Record and type the fully qualified domain name (FQDN) (for example, machine.proto.nc.ms.com) of the DNS server to which the subzone will be delegated.

  7. Select the zone and refresh; the delegation is now active.

If you follow the same steps as above, but reverse step four and step six (create the NS record before the A record), you will need to restart the DNS server service--the delegation is not active until the DNS server service is stopped and restarted.


Additional query words: prodnt ntdns
Keywords : kbbug4.00 kbfix4.00.sp2 nttcp kbnetwork
Version : 4.0
Platform : winnt


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.