missing dns records such as _msdcs and getting error 5781 on win2k dc

hi,

users cannot join the domain due to dns issues.....the server is missing
records such as _msdcs and getting eventID error 5781 on a win2k dc

how I populate DNS with all the required srv and _msdcs records since all
there is now is one A record for the server


Marc

Restart the Netlogon service on the DC's with missing records.

SB


"Marc I." <[email protected]> wrote in message
news:O%[email protected]...
> hi,
>
> users cannot join the domain due to dns issues.....the server is missing
> records such as _msdcs and getting eventID error 5781 on a win2k dc
>
> how I populate DNS with all the required srv and _msdcs records since all
> there is now is one A record for the server
>
>
> Marc
>

Restart the Netlogon service on the DC's with missing records.

SB


"Marc I." <[email protected]> wrote in message
news:O%[email protected]...
> hi,
>
> users cannot join the domain due to dns issues.....the server is missing
> records such as _msdcs and getting eventID error 5781 on a win2k dc
>
> how I populate DNS with all the required srv and _msdcs records since all
> there is now is one A record for the server
>
>
> Marc
>

Restart the Netlogon service on the DC's with missing records.

SB


"Marc I." <[email protected]> wrote in message
news:O%[email protected]...
> hi,
>
> users cannot join the domain due to dns issues.....the server is missing
> records such as _msdcs and getting eventID error 5781 on a win2k dc
>
> how I populate DNS with all the required srv and _msdcs records since all
> there is now is one A record for the server
>
>
> Marc
>

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX) couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:[email protected]...
> Restart the Netlogon service on the DC's with missing records.
>
> SB
>
>
> "Marc I." <[email protected]> wrote in message
> news:O%[email protected]...
>> hi,
>>
>> users cannot join the domain due to dns issues.....the server is missing
>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>
>> how I populate DNS with all the required srv and _msdcs records since all
>> there is now is one A record for the server
>>
>>
>> Marc
>>
>
>

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX) couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:[email protected]...
> Restart the Netlogon service on the DC's with missing records.
>
> SB
>
>
> "Marc I." <[email protected]> wrote in message
> news:O%[email protected]...
>> hi,
>>
>> users cannot join the domain due to dns issues.....the server is missing
>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>
>> how I populate DNS with all the required srv and _msdcs records since all
>> there is now is one A record for the server
>>
>>
>> Marc
>>
>
>

This windows 2000 single DC has its primary IP pointed to itself see below
for more info

Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

C:\>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\TESTRADIX01
Starting test: Connectivity
TESTRADIX01's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX) couldn't
be
resolved, the server name (testradix01.IHSTESTRADIX) resolved to
the
IP address (192.168.92.98) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... TESTRADIX01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TESTRADIX01
Skipping all tests, because server TESTRADIX01 is
not responding to directory service requests

Running enterprise tests on : IHSTESTRADIX
Starting test: Intersite
......................... IHSTESTRADIX passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
135
5
A Good Time Server could not be located.
......................... IHSTESTRADIX failed test FsmoCheck

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:[email protected]...
> Restart the Netlogon service on the DC's with missing records.
>
> SB
>
>
> "Marc I." <[email protected]> wrote in message
> news:O%[email protected]...
>> hi,
>>
>> users cannot join the domain due to dns issues.....the server is missing
>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>
>> how I populate DNS with all the required srv and _msdcs records since all
>> there is now is one A record for the server
>>
>>
>> Marc
>>
>
>

set the servers DNS server configuration address to 127.0.0.1 as it hosts
DNS and see if this fixes the issue.

Mark
"Marc I." <[email protected]> wrote in message
news:ex%[email protected]...
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
> C:\>dcdiag
>
> DC Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial non skippeable tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Starting test: Connectivity
> TESTRADIX01's server GUID DNS name could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX)
> couldn't be
> resolved, the server name (testradix01.IHSTESTRADIX) resolved to
> the
> IP address (192.168.92.98) and was pingable. Check that the IP
> address is registered correctly with the DNS server.
> ......................... TESTRADIX01 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Skipping all tests, because server TESTRADIX01 is
> not responding to directory service requests
>
> Running enterprise tests on : IHSTESTRADIX
> Starting test: Intersite
> ......................... IHSTESTRADIX passed test Intersite
> Starting test: FsmoCheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 135
> 5
> A Good Time Server could not be located.
> ......................... IHSTESTRADIX failed test FsmoCheck
>
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:[email protected]...
>> Restart the Netlogon service on the DC's with missing records.
>>
>> SB
>>
>>
>> "Marc I." <[email protected]> wrote in message
>> news:O%[email protected]...
>>> hi,
>>>
>>> users cannot join the domain due to dns issues.....the server is missing
>>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>>
>>> how I populate DNS with all the required srv and _msdcs records since
>>> all there is now is one A record for the server
>>>
>>>
>>> Marc
>>>
>>
>>
>
>

set the servers DNS server configuration address to 127.0.0.1 as it hosts
DNS and see if this fixes the issue.

Mark
"Marc I." <[email protected]> wrote in message
news:ex%[email protected]...
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
> C:\>dcdiag
>
> DC Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial non skippeable tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Starting test: Connectivity
> TESTRADIX01's server GUID DNS name could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX)
> couldn't be
> resolved, the server name (testradix01.IHSTESTRADIX) resolved to
> the
> IP address (192.168.92.98) and was pingable. Check that the IP
> address is registered correctly with the DNS server.
> ......................... TESTRADIX01 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Skipping all tests, because server TESTRADIX01 is
> not responding to directory service requests
>
> Running enterprise tests on : IHSTESTRADIX
> Starting test: Intersite
> ......................... IHSTESTRADIX passed test Intersite
> Starting test: FsmoCheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 135
> 5
> A Good Time Server could not be located.
> ......................... IHSTESTRADIX failed test FsmoCheck
>
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:[email protected]...
>> Restart the Netlogon service on the DC's with missing records.
>>
>> SB
>>
>>
>> "Marc I." <[email protected]> wrote in message
>> news:O%[email protected]...
>>> hi,
>>>
>>> users cannot join the domain due to dns issues.....the server is missing
>>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>>
>>> how I populate DNS with all the required srv and _msdcs records since
>>> all there is now is one A record for the server
>>>
>>>
>>> Marc
>>>
>>
>>
>
>

set the servers DNS server configuration address to 127.0.0.1 as it hosts
DNS and see if this fixes the issue.

Mark
"Marc I." <[email protected]> wrote in message
news:ex%[email protected]...
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
> C:\>dcdiag
>
> DC Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial non skippeable tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Starting test: Connectivity
> TESTRADIX01's server GUID DNS name could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (e368693c-4cce-4d33-8528-3395b1f04a00._msdcs.IHSTESTRADIX)
> couldn't be
> resolved, the server name (testradix01.IHSTESTRADIX) resolved to
> the
> IP address (192.168.92.98) and was pingable. Check that the IP
> address is registered correctly with the DNS server.
> ......................... TESTRADIX01 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\TESTRADIX01
> Skipping all tests, because server TESTRADIX01 is
> not responding to directory service requests
>
> Running enterprise tests on : IHSTESTRADIX
> Starting test: Intersite
> ......................... IHSTESTRADIX passed test Intersite
> Starting test: FsmoCheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 135
> 5
> A Good Time Server could not be located.
> ......................... IHSTESTRADIX failed test FsmoCheck
>
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:[email protected]...
>> Restart the Netlogon service on the DC's with missing records.
>>
>> SB
>>
>>
>> "Marc I." <[email protected]> wrote in message
>> news:O%[email protected]...
>>> hi,
>>>
>>> users cannot join the domain due to dns issues.....the server is missing
>>> records such as _msdcs and getting eventID error 5781 on a win2k dc
>>>
>>> how I populate DNS with all the required srv and _msdcs records since
>>> all there is now is one A record for the server
>>>
>>>
>>> Marc
>>>
>>
>>
>
>

"Shiny Bob" <[email protected]> wrote in message
news:[email protected]:
> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>
> DNS and see if this fixes the issue.
>

Big fat NO - don't do that. He's supposed to put in the
TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
cause issues!

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"Shiny Bob" <[email protected]> wrote in message
news:[email protected]:
> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>
> DNS and see if this fixes the issue.
>

Big fat NO - don't do that. He's supposed to put in the
TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
cause issues!

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"Shiny Bob" <[email protected]> wrote in message
news:[email protected]:
> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>
> DNS and see if this fixes the issue.
>

Big fat NO - don't do that. He's supposed to put in the
TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
cause issues!

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"Marc I." <[email protected]> wrote in message
news:[email protected]:
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
Hi Marc,

Are you really having a single-label domain name (like "mydomain"
instead of "mydomain.com") as dns-domainname?
Is the DNS-Server Service installed and running?

Does the Forward-Lookup-Zone (same as the dns-domainname) exist?

Is it set to allow dynamic updates?

Is there a zone _msdcs.yourdomainname.com, or is _msdcs underneath the
zone yourdomainname.com?

If there's a _msdcs... Zone, is it configured to allow dynamic updates?

If you canged anything above, restart the netlogon-service on all DCs.

Verify that there's a CNAME-Entry underneath _msdcs with a GUID.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"Marc I." <[email protected]> wrote in message
news:[email protected]:
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
Hi Marc,

Are you really having a single-label domain name (like "mydomain"
instead of "mydomain.com") as dns-domainname?
Is the DNS-Server Service installed and running?

Does the Forward-Lookup-Zone (same as the dns-domainname) exist?

Is it set to allow dynamic updates?

Is there a zone _msdcs.yourdomainname.com, or is _msdcs underneath the
zone yourdomainname.com?

If there's a _msdcs... Zone, is it configured to allow dynamic updates?

If you canged anything above, restart the netlogon-service on all DCs.

Verify that there's a CNAME-Entry underneath _msdcs with a GUID.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"Marc I." <[email protected]> wrote in message
news:[email protected]:
> This windows 2000 single DC has its primary IP pointed to itself see below
> for more info
>
> Dynamic registration or deregistration of one or more DNS records failed
> because no DNS servers are available.
>
Hi Marc,

Are you really having a single-label domain name (like "mydomain"
instead of "mydomain.com") as dns-domainname?
Is the DNS-Server Service installed and running?

Does the Forward-Lookup-Zone (same as the dns-domainname) exist?

Is it set to allow dynamic updates?

Is there a zone _msdcs.yourdomainname.com, or is _msdcs underneath the
zone yourdomainname.com?

If there's a _msdcs... Zone, is it configured to allow dynamic updates?

If you canged anything above, restart the netlogon-service on all DCs.

Verify that there's a CNAME-Entry underneath _msdcs with a GUID.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

Are you sure this is a big fat no no -

http://www.tek-tips.com/faqs.cfm?fid=4017

2. Ensure DNS server on win2k is configured to permit dynamic updates.
Ensure the win2k server points to itself as a DNS server using 127.0.0.1 as
the DNS address.

http://www.microsoft.com/technet/pro.../domcntrl.mspx

Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close
to continue.

I have worked for several banks and they have configured their DNS like this
and this is where I learned this snippet from.

Mark



"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:%[email protected]...

> "Shiny Bob" <[email protected]> wrote in message
> news:[email protected]:
>> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>>
>> DNS and see if this fixes the issue.
>>
>
> Big fat NO - don't do that. He's supposed to put in the
> TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
> cause issues!
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org

Are you sure this is a big fat no no -

http://www.tek-tips.com/faqs.cfm?fid=4017

2. Ensure DNS server on win2k is configured to permit dynamic updates.
Ensure the win2k server points to itself as a DNS server using 127.0.0.1 as
the DNS address.

http://www.microsoft.com/technet/pro.../domcntrl.mspx

Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close
to continue.

I have worked for several banks and they have configured their DNS like this
and this is where I learned this snippet from.

Mark



"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:%[email protected]...

> "Shiny Bob" <[email protected]> wrote in message
> news:[email protected]:
>> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>>
>> DNS and see if this fixes the issue.
>>
>
> Big fat NO - don't do that. He's supposed to put in the
> TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
> cause issues!
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org

Are you sure this is a big fat no no -

http://www.tek-tips.com/faqs.cfm?fid=4017

2. Ensure DNS server on win2k is configured to permit dynamic updates.
Ensure the win2k server points to itself as a DNS server using 127.0.0.1 as
the DNS address.

http://www.microsoft.com/technet/pro.../domcntrl.mspx

Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close
to continue.

I have worked for several banks and they have configured their DNS like this
and this is where I learned this snippet from.

Mark



"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:%[email protected]...

> "Shiny Bob" <[email protected]> wrote in message
> news:[email protected]:
>> set the servers DNS server configuration address to 127.0.0.1 as it hosts
>>
>> DNS and see if this fixes the issue.
>>
>
> Big fat NO - don't do that. He's supposed to put in the
> TCP/IP-Properties the own IP-Adress, not the loopback adress. This will
> cause issues!
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

Yes, it's recommended you always use the correct IP and not the loopback
address -even though the GUI sometimes then displays the loopback in the
TCP/IP properties.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:[email protected]...
"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

Yes, it's recommended you always use the correct IP and not the loopback
address -even though the GUI sometimes then displays the loopback in the
TCP/IP properties.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:[email protected]...
"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

Yes, it's recommended you always use the correct IP and not the loopback
address -even though the GUI sometimes then displays the loopback in the
TCP/IP properties.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

"Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
message news:[email protected]...
"<Shiny Bob>" <parris@newsguy,com> wrote in message
news:parris@newsguy,com:
> Are you sure this is a big fat no no -
>
> http://www.tek-tips.com/faqs.cfm?fid=4017
>
> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
> as
> the DNS address.
>
>
> http://www.microsoft.com/technet/pro.../technologies/
> directory/activedirectory/stepbystep/domcntrl.mspx
>
> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
> Close
> to continue.
>
> I have worked for several banks and they have configured their DNS like
> this
> and this is where I learned this snippet from.
>

Hi Mark,

Issues I know of is that if you are using 127.0.0.1 they might populate
that in the dns-zone via dynamic updates. If a client is requesting the
record it's receiveing the loopback-adress and pointing to itself now.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing entries


"ptwilliams" <[email protected]> wrote in message
news:%[email protected]...
> Yes, it's recommended you always use the correct IP and not the loopback
> address -even though the GUI sometimes then displays the loopback in the
> TCP/IP properties.
>
> --
>
> Paul Williams
>
> http://www.msresource.net/
> http://forums.msresource.net/
>
> "Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
> message news:[email protected]...
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:parris@newsguy,com:
>> Are you sure this is a big fat no no -
>>
>> http://www.tek-tips.com/faqs.cfm?fid=4017
>>
>> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
>> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
>> as
>> the DNS address.
>>
>>
>> http://www.microsoft.com/technet/pro.../technologies/
>> directory/activedirectory/stepbystep/domcntrl.mspx
>>
>> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
>> Close
>> to continue.
>>
>> I have worked for several banks and they have configured their DNS like
>> this
>> and this is where I learned this snippet from.
>>
>
> Hi Mark,
>
> Issues I know of is that if you are using 127.0.0.1 they might populate
> that in the dns-zone via dynamic updates. If a client is requesting the
> record it's receiveing the loopback-adress and pointing to itself now.
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org
>
>

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing entries


"ptwilliams" <[email protected]> wrote in message
news:%[email protected]...
> Yes, it's recommended you always use the correct IP and not the loopback
> address -even though the GUI sometimes then displays the loopback in the
> TCP/IP properties.
>
> --
>
> Paul Williams
>
> http://www.msresource.net/
> http://forums.msresource.net/
>
> "Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
> message news:[email protected]...
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:parris@newsguy,com:
>> Are you sure this is a big fat no no -
>>
>> http://www.tek-tips.com/faqs.cfm?fid=4017
>>
>> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
>> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
>> as
>> the DNS address.
>>
>>
>> http://www.microsoft.com/technet/pro.../technologies/
>> directory/activedirectory/stepbystep/domcntrl.mspx
>>
>> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
>> Close
>> to continue.
>>
>> I have worked for several banks and they have configured their DNS like
>> this
>> and this is where I learned this snippet from.
>>
>
> Hi Mark,
>
> Issues I know of is that if you are using 127.0.0.1 they might populate
> that in the dns-zone via dynamic updates. If a client is requesting the
> record it's receiveing the loopback-adress and pointing to itself now.
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org
>
>

I created a new forward zone called " _msdcs.domainname " and cycled the
netlogon service which resolved the issue and populated all missing entries


"ptwilliams" <[email protected]> wrote in message
news:%[email protected]...
> Yes, it's recommended you always use the correct IP and not the loopback
> address -even though the GUI sometimes then displays the loopback in the
> TCP/IP properties.
>
> --
>
> Paul Williams
>
> http://www.msresource.net/
> http://forums.msresource.net/
>
> "Ulf B. Simon-Weidner [MVP]" <[email protected]> wrote in
> message news:[email protected]...
> "<Shiny Bob>" <parris@newsguy,com> wrote in message
> news:parris@newsguy,com:
>> Are you sure this is a big fat no no -
>>
>> http://www.tek-tips.com/faqs.cfm?fid=4017
>>
>> 2. Ensure DNS server on win2k is configured to permit dynamic updates.
>> Ensure the win2k server points to itself as a DNS server using 127.0.0.1
>> as
>> the DNS address.
>>
>>
>> http://www.microsoft.com/technet/pro.../technologies/
>> directory/activedirectory/stepbystep/domcntrl.mspx
>>
>> Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click
>> Close
>> to continue.
>>
>> I have worked for several banks and they have configured their DNS like
>> this
>> and this is where I learned this snippet from.
>>
>
> Hi Mark,
>
> Issues I know of is that if you are using 127.0.0.1 they might populate
> that in the dns-zone via dynamic updates. If a client is requesting the
> record it's receiveing the loopback-adress and pointing to itself now.
>
> --
> Gruesse - Sincerely,
>
> Ulf B. Simon-Weidner
>
> MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
> Weblog: http://msmvps.org/UlfBSimonWeidner
> WebSite: http://www.windowsserverfaq.org
>
>

Same problem, resolved:
New Server w/ W2000 Adv Server, SP4.
Setup exactly like the previous server. (Basically a hardware upgrade)

The problem described was caused because I did not have the server's IP address in the local network IP as the DNS server.
I added it and placed it at the top above the other two DNS addresses provided by the DSL provider and then did a restart on the DNS service, then a restart on the Logon Service. Everything appeard as it should have.

In the future, I'll install the Server OS, then the drivers, then set the DNS single entry to the server. Then, run DCPROMO. Later, I'll add in the two outside DNS servers, BELOW the local DNS server.

In news:[email protected],
MattBowers <[email protected]> typed:
> Same problem, resolved:
> New Server w/ W2000 Adv Server, SP4.
> Setup exactly like the previous server. (Basically a hardware upgrade)
>
> The problem described was caused because I did not have the server's
> IP address in the local network IP as the DNS server.
> I added it and placed it at the top above the other two DNS addresses
> provided by the DSL provider and then did a restart on the DNS
> service, then a restart on the Logon Service. Everything appeard as
> it should have.
>
> In the future, I'll install the Server OS, then the drivers, then set
> the DNS single entry to the server. Then, run DCPROMO. Later, I'll
> add in the two outside DNS servers, BELOW the local DNS server.

I don't know what transpired in your thread, but as an FYI, NEVER use any
other DNS server other than the DNS server that hosts the AD zone or expect
numerous problems. Remove the IPs the DSL provider gave you. ONLY have your
internal DNS server in all machines' IP properties ONLY. Go to your DNS
server, open the DNS console, rt-click the server name, choose properties,
choose the Forwarding tab, and supply those DNS addresses the DSL provider
gave you. Click Ok and you're good to go with efficient inside resolution so
you can insure AD works properly, as well as outside resolution where your
DNS server is forcing the DSL provider's DNS to resolve outside n ames for
you.

If not sure how to follow those steps, please read the following article. I
also supplied a 'best practice' to help guide you with DNS.

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003
(forwarding) :
http://support.microsoft.com/?id=323380

300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000
(forwarding) :
http://support.microsoft.com/?id=300202

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/?id=825036


Here are additional links to help, in case you may have a single label name
domain, or a mismatched Primary DNS Suffix that doesn't match the AD zone
name in DNS.

Domain Controller's Domain Name System Suffix Does Not Match Domain Name:
http://support.microsoft.com/?id=257623

Clients cannot dynamically register DNS records in a single-label forward
lookup zone:
http://support.microsoft.com/?id=826743

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/?id=300684


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations