Deregistration of DNS records Failed

  • Thread starter Thread starter -- Paul --
  • Start date Start date
P

-- Paul --

Hello,



I have recently run dspromo on a Win2K Server and changed the Domain info.
Now I am getting the following error in the 'System' event log. Not sure
how to get rid of these. Any help appreciated.



Thanks



Paul



Event Type: Error

Event Source: NETLOGON

Event Category: None

Event ID: 5775

Date: 25/10/2003

Time: 17:22:57

User: N/A

Computer: ADDER

Description:

Deregistration of the DNS record
'_ldap._tcp.Default-First-Site._sites.gc._msdcs.May.coinsider.com. 600 IN
SRV 0 100 3268 adder.May.coinsider.com.' failed with the following error:

DNS server unable to interpret format.

Data:

0000: 29 23 00 00 )#..



Event Type: Error

Event Source: NETLOGON

Event Category: None

Event ID: 5775

Date: 25/10/2003

Time: 17:27:35

User: N/A

Computer: ADDER

Description:

Deregistration of the DNS record '_ldap._tcp.dc._msdcs.May.coinsider.com.
600 IN SRV 0 100 389 adder.May.coinsider.com.' failed with the following
error:

DNS server unable to interpret format.

Data:

0000: 29 23 00 00 )#..





Event Type: Error

Event Source: NETLOGON

Event Category: None

Event ID: 5775

Date: 25/10/2003

Time: 17:27:37

User: N/A

Computer: ADDER

Description:

Deregistration of the DNS record
'_gc._tcp.Default-First-Site._sites.May.coinsider.com. 600 IN SRV 0 100 3268
adder.May.coinsider.com.' failed with the following error:

DNS server unable to interpret format.

Data:

0000: 29 23 00 00 )#..
 
In
-- Paul -- said:
Hello,



I have recently run dspromo on a Win2K Server and changed the Domain
info. Now I am getting the following error in the 'System' event log.
Not sure how to get rid of these. Any help appreciated.
Click to expand...


These error are generally caused from using your ISP's DNS in your NIC
TCP/IP properties use only your internal DNS server on all NICs on all
machines in an AD Domain. For internet access configure DNS as per this KB
article: 300202 - HOW TO Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1

If pointing only to the internal DNS does not makes the errors go away you
may have a disjointed name space post an ipconfig /all AND the actual domain
name in ADU&C so we can start to diagnose the problem.
 
Thanks for your help.

I have followed the instructions in the KB article you suggested, but the
problem still exists.

The actual domain name shown in ADU&C is adder.mayhem.local.
Previouly it was adder.mayhem.considered.biz
Here is the ipconfig/all details:-


Windows 2000 IP Configuration

Host Name adder
Primary DNS Suffix mayhem.local
Node Type Broadcast
IP Routing Enabled No
Wins Proxy Enabled No
DNS Suffix Search List mayhem.local

Ethernet adapter Local Area Connection

Connection Specific DNS Suffix
Description 3com Etherlink
Physical Address 00.01.02.DC.77.03
DHCP Enabled No
IP Address 10.10.1.1
Subnet 255.0.0.0
Default Gateway 10.0.0.1
DNS Servers 10.10.1.1

Regards
Paul
 
In
-- Paul -- said:
Thanks for your help.

I have followed the instructions in the KB article you suggested, but
the problem still exists.

The actual domain name shown in ADU&C is adder.mayhem.local.
Previouly it was adder.mayhem.considered.biz
Here is the ipconfig/all details:-


Windows 2000 IP Configuration

Host Name adder
Primary DNS Suffix mayhem.local
Node Type Broadcast
IP Routing Enabled No
Wins Proxy Enabled No
DNS Suffix Search List mayhem.local

Ethernet adapter Local Area Connection

Connection Specific DNS Suffix
Description 3com Etherlink
Physical Address 00.01.02.DC.77.03
DHCP Enabled No
IP Address 10.10.1.1
Subnet 255.0.0.0
Default Gateway 10.0.0.1
DNS Servers 10.10.1.1

Regards
Paul
Click to expand...
The ipconfig looks ok.

Below are some basic rules for registration (#5 and 6 don't seem to apply to
you). Curious how you went about changing the domain name for AD? Did you
reinstall it or demote it and re-promote it?

1. Primary DNS Suffix needs to match the AD DNS Domain name (as it shows up
in ADUC) exactly. The netlogon service enumerates the service records and
resource locations from the AD database then uses the Primary DNS Suffix to
send the registration to under that zone name.
2. The zone name in DNS must match the above two names exactly.
3. Dynamic Updates are enabled on the zone properties. (Set to at least
"YES").
4. The machine needs to be pointing to itself for DNS.

5. If the AD DNS Domain name is a single label name, then registration
problems will occur if you have SP4 or newer installed on W2k. You can
bandaid this on the server, but it will NOT help your XP Pro clients since
they have problems querying single label names. An example of a single label
DNS name is "domain" rather than "domain.com". Read this article on how to
overcome this limitation on your DCs and DNS servers. As I said this will
not help XP.
http://support.microsoft.com/?id=300684

6. All machines in an AD environment need to be using the internal DNS
server only. DO NOT use your ISP's DNS server or your router at all as a DNS
entry in your IP properties. If you do, numerous errors will occur. The Root
Hints will allow for Internet resolution, but to achieve efficient Internet
resolution, recommended to configure a Forwarder. If the Forwarding option
is grayed out, then delete the Root zone. It look like a period ("."). This
article shows how to do delete the Root zone and to configure a forwarder:
http://support.microsoft.com/?id=300202


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thank you.

I cannot remember exactly how I changed the domain name. This is a test
server I have been learning with over the last few days. I think I demoted,
then promoted with a new domain name. This created DNS zones for a root
server for some reason?? The forwarder tab was greyed out because of this.
To get around this I deleted all the zones and recreated them I think.
Sorry I can't be more accurate, this is all new to me.

Anyway the event log entries refer to the old domain name, before I demoted
then promoted again. I think I probably went about this in totally the
wrong way which is why I know have the problem. I have followed through
those pointers you gave. The DNS suffix does match the AD DNS name and the
zone name. Dynamic updates are set to 'yes' and the machine points to itself
for DNS.

I can get drastic if necessary and delete the DNS service, and demote the
server etc, but can you advise me perhaps what is the correct order to do
all this in (if you think it is the way forward), so I don't get problems
again.

Appreciated

Paul


"Ace Fekay [MVP]"
 
In
-- Paul -- said:
Thanks for your help.

I have followed the instructions in the KB article you suggested, but
the problem still exists.

The actual domain name shown in ADU&C is adder.mayhem.local.
Previouly it was adder.mayhem.considered.biz
Click to expand...

If the domain name in ADU&C is adder.mayhem.local the problem is a
disjointed namespace, your primary DNS suffix must match that name. I can
tell you what happened when you chose the FQDN for this domain in DCPROMO
you included the server host name in it. Your only choice is to demote it a
promote it it with the correct name or live with it as is and correct the
primary DNS suffix.
 
Thanks for you patience guys. The utimate problem is my lack of knowledge
here. Perhaps I have misunderstood. Please let me clarify.

When I open ADU&C and click on the first item listed at the top of the left
hand pane which reads, Active Directory Users and Computers
[adder.mayhem.local], the right hand pane, under the 'Name' column says
mayhem.local. Additionally, if I right click my computer and go to
properties > network id it reads, 'Full Computer Name' - adder.mayhem.local
and then 'Domain' - mayhem.local.

I know I said before that 'The actual domain name shown in ADU&C is
adder.mayhem.local', but I think I mistakenly put the host name on the front
of the domain name.

That said, what you have said is probably incorrect. Sorry to mess around

I think I will just demote, remove the dns service, reboot, reinstall dns
service and configure it, then promote again.

What do you reckon?

Obliged
Paul
 
In
-- Paul -- said:
Thanks for you patience guys. The utimate problem is my lack of
knowledge here. Perhaps I have misunderstood. Please let me clarify.

When I open ADU&C and click on the first item listed at the top of
the left hand pane which reads, Active Directory Users and Computers
[adder.mayhem.local], the right hand pane, under the 'Name' column
says mayhem.local. Additionally, if I right click my computer and go
to properties > network id it reads, 'Full Computer Name' -
adder.mayhem.local and then 'Domain' - mayhem.local.

I know I said before that 'The actual domain name shown in ADU&C is
adder.mayhem.local', but I think I mistakenly put the host name on
the front of the domain name.

That said, what you have said is probably incorrect. Sorry to mess
around

I think I will just demote, remove the dns service, reboot, reinstall
dns service and configure it, then promote again.

What do you reckon?
Click to expand...

OK, there is some confusion here if the domain in ADU&C is mayhem.local then
it is OK and you don't have to DCPROMO because that is your primary DNS
suffix.
Let's see if we can clean up any errors, if you can post a netdiag /test:dns
/v it will give a big clue as to where the problem might be.
 
In
-- Paul -- said:
Thank you.

I cannot remember exactly how I changed the domain name. This is a
test server I have been learning with over the last few days. I
think I demoted, then promoted with a new domain name. This created
DNS zones for a root server for some reason?? The forwarder tab was
greyed out because of this. To get around this I deleted all the
zones and recreated them I think. Sorry I can't be more accurate,
this is all new to me.

Anyway the event log entries refer to the old domain name, before I
demoted then promoted again. I think I probably went about this in
totally the wrong way which is why I know have the problem. I have
followed through those pointers you gave. The DNS suffix does match
the AD DNS name and the zone name. Dynamic updates are set to 'yes'
and the machine points to itself for DNS.

I can get drastic if necessary and delete the DNS service, and demote
the server etc, but can you advise me perhaps what is the correct
order to do all this in (if you think it is the way forward), so I
don't get problems again.

Appreciated

Paul
Click to expand...

Paul,

This is getting confusing along with some mayhem here. Kind of like what
Dallas is experiencing against the Bucs at this moment. I know Kevin doesn't
like that! :-)

Anyway, let's try this:
Delete the zone called mayhem.local
Delete the system32\netlogon.dns and .dnb files.
Recreate the mayhem.local zone
Enable updates
In a cmd prompt:
ipconfig /registerdns
net stop netlogon
net start netlogon
Then run what Kevin suggested with the netdiag command.

If that doesn;t work, they I would say since this a test server, why not
just delete the whole mess? Demote it then uninstall DNS. If it won't demote
properly, follow this article (I have this 5 meg file if you need it):
332199 - Using the DCPROMO -FORCEREMOVAL Command to Force the Demotion of
Active Directory Domain Controllers:
http://support.microsoft.com/?id=332199

Then set the Primary DNS Suffix on the machine to the new domain name. Call
it mayhem.paul. Then create the zone in DNS. Then point to itself. Then run
DCPROMO and choose mayhem.paul as the AD DNS Domain name, and choose MAYHEM
as the NETBIOS name.

Ok, back to watching that slaughter, err I mean game...
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Appreciate your help. I have installed 2000 Server on another faster
machine and removed it from the old machine that was playing up. The
problem obviously no longer exists.

Cheers Though


Kevin D. Goodknecht said:
In
-- Paul -- said:
Thanks for you patience guys. The utimate problem is my lack of
knowledge here. Perhaps I have misunderstood. Please let me clarify.

When I open ADU&C and click on the first item listed at the top of
the left hand pane which reads, Active Directory Users and Computers
[adder.mayhem.local], the right hand pane, under the 'Name' column
says mayhem.local. Additionally, if I right click my computer and go
to properties > network id it reads, 'Full Computer Name' -
adder.mayhem.local and then 'Domain' - mayhem.local.

I know I said before that 'The actual domain name shown in ADU&C is
adder.mayhem.local', but I think I mistakenly put the host name on
the front of the domain name.

That said, what you have said is probably incorrect. Sorry to mess
around

I think I will just demote, remove the dns service, reboot, reinstall
dns service and configure it, then promote again.

What do you reckon?
Click to expand...

OK, there is some confusion here if the domain in ADU&C is mayhem.local then
it is OK and you don't have to DCPROMO because that is your primary DNS
suffix.
Let's see if we can clean up any errors, if you can post a netdiag /test:dns
/v it will give a big clue as to where the problem might be.
Click to expand...
 
In
-- Paul -- said:
Appreciate your help. I have installed 2000 Server on another faster
machine and removed it from the old machine that was playing up. The
problem obviously no longer exists.

Cheers Though
Click to expand...

Sounds good. Glad to hear you got it going, one way or another.
Cheers back to you!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top