old DNS records still coming up after AD reinstall

  • Thread starter Thread starter JiGZ
  • Start date Start date
J

JiGZ

Hello,

I was having some trouble with our system and decided to unistall
active directory as well as DNS and start over from scratch. I even
went as far as changing the server's computer name as well as the
domain name. I am running a stand-alone Win2k Server with a router
connecting the other pc's in the office and for internet access (DSL).

After I reinstalled Active Dir and DNS, I then deleted the "." fwd
lookup zone and added my router as a fwder for internet access (which
isn't working)...

The internet will not work now throughout the office and the event
viewer keeps spitting errors referring to the server's old name and old
domain name before I reinstalled everything.

Any help would be much appreciated.

My old pc name and domain: mlserver.mlglass.com
My new pc name and domain: compass1.compass.ca

I have included a couple of the error events below:


ERROR EVENTS:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:43:42 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record
'_ldap._tcp.84a0798c-590e-4561-b6fd-b593c89c3b08.domains._msdcs.mlglass.com.
600 IN SRV 0 100 389 mlserver.mlglass.com.' failed with the following
error:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:42:48 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record '_ldap._tcp.mlglass.com. 600 IN SRV 0
100 389 mlserver.mlevyglass.com.' failed with the following error:
DNS server unable to interpret format.

THANKS FOR ANY HELP!!!
Jake.
 
JiGZ said:
Hello,

I was having some trouble with our system and decided to unistall
active directory as well as DNS and start over from scratch. I even
went as far as changing the server's computer name as well as the
domain name. I am running a stand-alone Win2k Server with a router
connecting the other pc's in the office and for internet access (DSL).
Click to expand...

If you have a DC then it is not "stand-alone" or if you have another
server that is in the domain neither is it. If you truly have a Domain
AND a stand-alone server than that server is largely irrelevant to
the domain.
After I reinstalled Active Dir and DNS, I then deleted the "." fwd
lookup zone and added my router as a fwder for internet access (which
isn't working)...
Click to expand...

You are flailing around instead of solving the problem or problems.

DNS is fairly easy to get right but also fairly easy to screw up if
you don't understand the basics.

Does your Router work correctly for DNS when you use NSLookup
and explicitly QUERY it?

nslookup www.google.com IP.Address.of.Router

Capture you "ipconfic /all" output from the DC and a sample
machine to a text and post them here.
The internet will not work now throughout the office and the event
viewer keeps spitting errors referring to the server's old name and old
domain name before I reinstalled everything.
Click to expand...

Sounds like you didn't really rename it. The name of a machine is ONLY
in the SYSTEM CONTROL PANEL where it must show both the base
name AND the DNS domain name (suffix.)


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

Any help would be much appreciated.

My old pc name and domain: mlserver.mlglass.com
My new pc name and domain: compass1.compass.ca

I have included a couple of the error events below:
Click to expand...
 
Thanks for the suggestions.

What I meant by stand-alone was that it is the only server in the
office, and Yes, I did rename the machine and created a new domain when
installing AD and DNS.

There are most likely a few directory's I should have deleted which
kept the old settings and are causing the conflict with the old server
name and domain name.

Don't get me wrong, I appreciate your comments, but I am not 'flailing
around'... my explanation may have not been detailed where I should
have mentioned that the various problems I stated are seperate ones and
not necessarily related ones, but I was a bit distressed while writing
this posting.

Jake.

Herb said:
JiGZ said:
Hello,

I was having some trouble with our system and decided to unistall
active directory as well as DNS and start over from scratch. I even
went as far as changing the server's computer name as well as the
domain name. I am running a stand-alone Win2k Server with a router
connecting the other pc's in the office and for internet access (DSL).
Click to expand...

If you have a DC then it is not "stand-alone" or if you have another
server that is in the domain neither is it. If you truly have a Domain
AND a stand-alone server than that server is largely irrelevant to
the domain.
After I reinstalled Active Dir and DNS, I then deleted the "." fwd
lookup zone and added my router as a fwder for internet access (which
isn't working)...
Click to expand...

You are flailing around instead of solving the problem or problems.

DNS is fairly easy to get right but also fairly easy to screw up if
you don't understand the basics.

Does your Router work correctly for DNS when you use NSLookup
and explicitly QUERY it?

nslookup www.google.com IP.Address.of.Router

Capture you "ipconfic /all" output from the DC and a sample
machine to a text and post them here.
The internet will not work now throughout the office and the event
viewer keeps spitting errors referring to the server's old name and old
domain name before I reinstalled everything.
Click to expand...

Sounds like you didn't really rename it. The name of a machine is ONLY
in the SYSTEM CONTROL PANEL where it must show both the base
name AND the DNS domain name (suffix.)


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

...or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

Any help would be much appreciated.

My old pc name and domain: mlserver.mlglass.com
My new pc name and domain: compass1.compass.ca

I have included a couple of the error events below:
Click to expand...



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
ERROR EVENTS:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:43:42 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record
'_ldap._tcp.84a0798c-590e-4561-b6fd-b593c89c3b08.domains._msdcs.mlglass.com.
600 IN SRV 0 100 389 mlserver.mlglass.com.' failed with the following
error:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:42:48 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record '_ldap._tcp.mlglass.com. 600 IN SRV 0
100 389 mlserver.mlevyglass.com.' failed with the following error:
DNS server unable to interpret format.

THANKS FOR ANY HELP!!!
Jake.
Click to expand...
Click to expand...
 
JiGZ said:
Thanks for the suggestions.

What I meant by stand-alone was that it is the only server in the
office, and Yes, I did rename the machine and created a new domain when
installing AD and DNS.
Click to expand...

Stand-alone is a long time technical term for a Windows
server which is NOT in a domain so that is where the
confusion lies.
There are most likely a few directory's I should have deleted which
kept the old settings and are causing the conflict with the old server
name and domain name.
Click to expand...

No, not likely. What directories?

A new install is a new install. A new domain is a new domain.
Don't get me wrong, I appreciate your comments, but I am not 'flailing
around'... my explanation may have not been detailed where I should
have mentioned that the various problems I stated are seperate ones and
not necessarily related ones, but I was a bit distressed while writing
this posting.
Click to expand...

Sorry, but trying to solve simple problems by re-installing is
a not an efficient method nor long term useful method.

It's popular but finding and learing how to fix the problem is
both more efficient and in the long run will teach you how to
solve these problems which are fairly common by those who
don't fully understand DNS and AD.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Jake.

Herb said:
JiGZ said:
Hello,

I was having some trouble with our system and decided to unistall
active directory as well as DNS and start over from scratch. I even
went as far as changing the server's computer name as well as the
domain name. I am running a stand-alone Win2k Server with a router
connecting the other pc's in the office and for internet access (DSL).
Click to expand...

If you have a DC then it is not "stand-alone" or if you have another
server that is in the domain neither is it. If you truly have a Domain
AND a stand-alone server than that server is largely irrelevant to
the domain.
After I reinstalled Active Dir and DNS, I then deleted the "." fwd
lookup zone and added my router as a fwder for internet access (which
isn't working)...
Click to expand...

You are flailing around instead of solving the problem or problems.

DNS is fairly easy to get right but also fairly easy to screw up if
you don't understand the basics.

Does your Router work correctly for DNS when you use NSLookup
and explicitly QUERY it?

nslookup www.google.com IP.Address.of.Router

Capture you "ipconfic /all" output from the DC and a sample
machine to a text and post them here.
The internet will not work now throughout the office and the event
viewer keeps spitting errors referring to the server's old name and old
domain name before I reinstalled everything.
Click to expand...

Sounds like you didn't really rename it. The name of a machine is ONLY
in the SYSTEM CONTROL PANEL where it must show both the base
name AND the DNS domain name (suffix.)


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or
indirectly)

netdiag /fix

...or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

Any help would be much appreciated.

My old pc name and domain: mlserver.mlglass.com
My new pc name and domain: compass1.compass.ca

I have included a couple of the error events below:
Click to expand...



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
ERROR EVENTS:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:43:42 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record
'_ldap._tcp.84a0798c-590e-4561-b6fd-b593c89c3b08.domains._msdcs.mlglass.com.
600 IN SRV 0 100 389 mlserver.mlglass.com.' failed with the following
error:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 8/23/06
Time: 1:42:48 PM
User: N/A
Computer: COMPASS1
Description:
Deregistration of the DNS record '_ldap._tcp.mlglass.com. 600 IN SRV 0
100 389 mlserver.mlevyglass.com.' failed with the following error:
DNS server unable to interpret format.

THANKS FOR ANY HELP!!!
Jake.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top