No DNS servers configured for local system.

Discussion in 'Server Networking' started by MikeV99, Oct 29, 2005.

  1. MikeV99

    MikeV99 Guest

    I get these on a regular basis. I would like to resolve them, but ...
    How can the local system run without a DNS server? Mine seems to be
    doing OK?

    Event Type: Warning
    Event Source: NETLOGON
    Event Category: None
    Event ID: 5782
    Date: 10/29/2005
    Time: 8:16:42 AM
    User: N/A
    Computer: WIN2003-HOME
    Description:
    Dynamic registration or deregistration of one or more DNS records
    failed with the following error:

    No DNS servers configured for local system.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 7c 26 00 00 |&..

    This help says

    Explanation
    The DNS server could not dynamically delete the DNS records.

    User Action
    To initiate dynamic deletion on the DNS server, do the following:

    Run DCDiag.exe.
    This program is located on your Windows Server 2003 CD in the
    Support\Tools folder.
    Fix any problems identified by DCDiag.exe.
    At the command prompt on the DC, type
    nltest.exe /dsregdns
    The Nttest.exe program is available on the Microsoft Windows Server
    2000 Resource Kit CD.

    However, the issue of dynamic deletion of of DNS records would seem to
    be different than the configuration of a DNS server for the local
    system.

    Everything passes when I run DCDiag except:

    C:\Work>dcdiag

    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\WIN2003-HOME
    Starting test: Connectivity
    The host
    fc6f4ee6-5726-4d23-8ab5-7dfece509647._msdcs.foo.com could not be
    resolved to an IP address. Check the DNS server, DHCP, server name,
    etc

    Although the Guid DNS name
    (fc6f4ee6-5726-4d23-8ab5-7dfece509647._msdcs.foo.com)
    couldn't be resolved, the server name (WIN2003-HOME.foo.com) resolved
    to the IP address (192.168.1.95) and was pingable.

    Check that the IP address is registered correctly with the DNS server.
    ......................... WIN2003-HOME failed test connectivity

    The DNS server looks OK ??

    The forward lookup zone for foo.com is running and contains

    Name Type Data
    _msdcs
    (same as parent folder) Start of Authority (SOA) [3],
    win2003-home.foo.com., hostmaster.
    (same as parent folder) Name Server (NS) win2003-home.foo.com.
    win2003-home Host (A) 192.168.1.95

    Everything seems to work OK except for the event log warnings.

    Any ideas?

    Thanks.
     
    MikeV99, Oct 29, 2005
    #1
    1. Advertisements

  2. MikeV99

    MikeV99 Guest

    Thanks, but I think I meet all the steps...

    1. If this the only DNS in the LAN, make sure the DNS point to itself
    instead of ISP DNS.

    The internal address is used in the DNS server (192...) only and the
    forward zone points to itself.

    2 If there are two DNS servers in the LAN, make sure they point to
    each other as primary and themselves as secondary.

    Only 1 DNS server in the LAN.

    3. If your machine is pointing to the ISP DNS, you may want to stop to
    register with the DNS. To do that, open the DNS tab of the advanced
    TCP/IP properties of the connection and uncheck Register this
    connection’s address in DNS.

    Always.

    4. Running NETDIAG /fix may fix the issue.

    The only copy I could find is for windows 2000 only.

    5. Make sure the DHCP Client be running in the problem computer.

    DHCP Client not needed since the system has a static internal ip
    address.

    Any other advice?

     
    MikeV99, Oct 30, 2005
    #2
    1. Advertisements

  3. MikeV99

    MikeV99 Guest

    Oh shoot ... I found the correct version...

    DNS test . . . . . . . . . . . . . : Failed
    [WARNING] The DNS entries for this DC are not registered correctly
    on DNS server 'external name server'. Please wait for 30 minutes for
    DNS server replication.

    OK, can you please point me somewhere that will help with that?

    I have a server on a LAN with internal ip address (DNS server & DC).
    It is connected to the internet via a router.

    The network connection tcp/ip properties point to the external name
    server and are set to not register.

    Where am I missing out in the DNS server for not pointing to its self?
    My zone records are at the bottom of this message.

    Thanks.

     
    MikeV99, Oct 30, 2005
    #3
  4. Try:

    1. "The network connection tcp/ip properties point to the external name
    server and are set to not register." If this is a DC/DNS server, then it
    must register its resource records in DNS; TCP/IP properties should be
    statically configured and must point to the Server's own IP, not some
    external server, for DNS. If you need Internet name resolution, configure
    Forwarders in the DNS mmc to point to your ISP's DNS server.

    2. "DHCP Client not needed since the system has a static internal ip
    address." The DHCP Client service is required in order to update DNS
    regardless of how TCP/IP is configured.

    Doug Sherman
    MCSE, MCSA, MCP+I, MVP

    deregistration of one or more DNS records failed with the following error:
    No DNS servers configured for local system...Resolutions...
     
    Doug Sherman [MVP], Oct 31, 2005
    #4
  5. MikeV99

    MikeV99 Guest

    Should have double checked, but the DHCP client is running.

     
    MikeV99, Oct 31, 2005
    #5
  6. MikeV99

    MikeV99 Guest

    I will go back and work on item 1 some more. Should have double
    checked, the DHCP client is running -- need more sleep <grin>.

    The last time I tried to configure I could not get DNS resolution to
    work for the local machine. I will try again.

    Thanks.

     
    MikeV99, Oct 31, 2005
    #6
  7. MikeV99

    MikeV99 Guest

    Just as a follow up. I had to do step 1. Then I needed to enable
    dynamic updates (secure) for the zones. Finally, I used dcdiag,
    netdiag, and nltest to get things hooked together and restarted
    netlogin to force the update. Things appear to be pretty clean now.

    Thanks for pointing me in the correct direction.
     
    MikeV99, Nov 5, 2005
    #7
    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.