No DNS servers configured for local system.

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.

You may need to re-configure the DNS settings based on the following troubleshooting solutions,

Event ID Troubleshooting Event ID: 5782 - Dynamic registration or deregistration of one or more DNS records failed with the following error: No DNS servers configured for local system...Resolutions...
www.chicagotech.net/wineventid.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"MikeV99" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
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.

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?

On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
<(E-Mail Removed)> wrote:

>You may need to re-configure the DNS settings based on the following troubleshooting solutions,
>
>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or deregistration of one or more DNS records failed with the following error: No DNS servers configured for local system...Resolutions...
> www.chicagotech.net/wineventid.htm
>
>
>
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "MikeV99" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> 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.

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.

On 30 Oct 2005 16:16:01 -0600, MikeV99 <(E-Mail Removed)> wrote:

>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?
>
>On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
><(E-Mail Removed)> wrote:
>
>>You may need to re-configure the DNS settings based on the following troubleshooting solutions,
>>
>>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or deregistration of one or more DNS records failed with the following error: No DNS servers configured for local system...Resolutions...
>> www.chicagotech.net/wineventid.htm
>>
>>
>>
>>Bob Lin, MS-MVP, MCSE & CNE
>>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>> "MikeV99" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>> 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.

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

"MikeV99" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
> On 30 Oct 2005 16:16:01 -0600, MikeV99 <(E-Mail Removed)> wrote:
>
> >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?
> >
> >On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
> ><(E-Mail Removed)> wrote:
> >
> >>You may need to re-configure the DNS settings based on the following
troubleshooting solutions,
> >>
> >>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or
deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system...Resolutions...
> >> www.chicagotech.net/wineventid.htm
> >>
> >>
> >>
> >>Bob Lin, MS-MVP, MCSE & CNE
> >>Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
> >>How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
> >> "MikeV99" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> >> 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.

Thank you, Doug for the input. That is correct. The DHCP client service is required for registration of DNS A record for computers with statically assigned IP addresses.

Quoted form http://www.chicagotech.net/Troublesh...hcpclient1.htm

Analysis: The DHCP client service is required for registration of DNS A record for computers with DHCP and statically assigned IP addresses. For that reason, the DHCP Client service is set to start automatically by default in Windows OS. The DHCP Client Service is also responsible for registering Dynamic DNS (DDNS) names in Windows 2000.

Note: If a DNS server with static IP is not running the DHCP Client, the server may receive Event ID 5782 with "No DNS servers configured for local system" error.

Related Topics

Troubleshooting DNS


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
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

"MikeV99" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
> On 30 Oct 2005 16:16:01 -0600, MikeV99 <(E-Mail Removed)> wrote:
>
> >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?
> >
> >On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
> ><(E-Mail Removed)> wrote:
> >
> >>You may need to re-configure the DNS settings based on the following
troubleshooting solutions,
> >>
> >>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or
deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system...Resolutions...
> >> www.chicagotech.net/wineventid.htm
> >>
> >>
> >>
> >>Bob Lin, MS-MVP, MCSE & CNE
> >>Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
> >>How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
> >> "MikeV99" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> >> 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.

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

On Sun, 30 Oct 2005 20:50:54 -0600, "Robert L [MS-MVP]"
<(E-Mail Removed)> wrote:

>Thank you, Doug for the input. That is correct. The DHCP client service is required for registration of DNS A record for computers with statically assigned IP addresses.
>
>Quoted form http://www.chicagotech.net/Troublesh...hcpclient1.htm
>
>Analysis: The DHCP client service is required for registration of DNS A record for computers with DHCP and statically assigned IP addresses. For that reason, the DHCP Client service is set to start automatically by default in Windows OS. The DHCP Client Service is also responsible for registering Dynamic DNS (DDNS) names in Windows 2000.
>
>Note: If a DNS server with static IP is not running the DHCP Client, the server may receive Event ID 5782 with "No DNS servers configured for local system" error.
>
>Related Topics
>
>Troubleshooting DNS
>
>
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> 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
>
> "MikeV99" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > 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.
> >
> > On 30 Oct 2005 16:16:01 -0600, MikeV99 <(E-Mail Removed)> wrote:
> >
> > >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?
> > >
> > >On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
> > ><(E-Mail Removed)> wrote:
> > >
> > >>You may need to re-configure the DNS settings based on the following
> troubleshooting solutions,
> > >>
> > >>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or
> deregistration of one or more DNS records failed with the following error:
> No DNS servers configured for local system...Resolutions...
> > >> www.chicagotech.net/wineventid.htm
> > >>
> > >>
> > >>
> > >>Bob Lin, MS-MVP, MCSE & CNE
> > >>Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> > >>How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> > >> "MikeV99" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > >> 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.

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.

On Sun, 30 Oct 2005 19:37:33 -0500, "Doug Sherman [MVP]"
<(E-Mail Removed)> wrote:

>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
>
>"MikeV99" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> 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.
>>
>> On 30 Oct 2005 16:16:01 -0600, MikeV99 <(E-Mail Removed)> wrote:
>>
>> >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?
>> >
>> >On Sat, 29 Oct 2005 20:53:57 -0500, "Robert L [MS-MVP]"
>> ><(E-Mail Removed)> wrote:
>> >
>> >>You may need to re-configure the DNS settings based on the following
>troubleshooting solutions,
>> >>
>> >>Event ID Troubleshooting Event ID: 5782 - Dynamic registration or
>deregistration of one or more DNS records failed with the following error:
>No DNS servers configured for local system...Resolutions...
>> >> www.chicagotech.net/wineventid.htm
>> >>
>> >>
>> >>
>> >>Bob Lin, MS-MVP, MCSE & CNE
>> >>Networking, Internet, Routing, VPN Troubleshooting on
>http://www.ChicagoTech.net
>> >>How to Setup Windows, Network, VPN & Remote Access on
>http://www.HowToNetworking.com
>> >> "MikeV99" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> >> 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.
>

On Sun, 30 Oct 2005 19:37:33 -0500, "Doug Sherman [MVP]"
<(E-Mail Removed)> wrote:

>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.
>

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.