Sign in with
Sign up | Sign in
Your question

The DNS server machine currently has no DNS domain name

Last response: in Windows 2000/NT
Share
Anonymous
September 16, 2004 5:46:41 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi

I get the following event in DNS. I tried what they said
but the properties tab is gryed out so i can not go to
properties. I tried to decommision the Dc but it give me
error that says:
Operation failed because:
Failed finding a suitable domain controller for the
domain
"the specified domain either does not exist or could not
be contacted"

The problem started that we had 4 DC 2 got decomisioned
and one stolen. The main DC was the stolen one, I wonder
if that is the issue, Had to put DNS and Dhcp on this
last remainig server.

Please help thanks

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 16/09/2004
Time: 09:55:40 AM
User: N/A
Computer: GGBDC01
Description:
The DNS server machine currently has no DNS domain name.
Its DNS name is a single label hostname with no domain
(example: "host" rather than "host.microsoft.com").

You might have forgotten to configure a primary DNS
domain for the server computer. For more information, see
either "DNS server log reference" or "To configure the
primary DNS suffix for a client computer" in the online
Help.

While the DNS server has only a single label name, all
zones created will have default records (SOA and NS)
created using only this single label name for the
server's hostname. This can lead to incorrect and failed
referrals when clients and other DNS servers use these
records to locate this server by name.

To correct this problem:
1) open ControlPanel
2) open System applet
3) select NetworkIdentification tab
4) click the "Properties" button and enter a domain
name or workgroup name; this name will be used as your
DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up
default records, substituting new DNS name of this
server, for old single label name. However, you should
review to make sure zone's SOA and NS records now
properly use correct domain name of this server.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Anonymous
September 16, 2004 12:23:29 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:20a101c49bc9$b022a9d0$a601280a@phx.gbl,
Piet <anonymous@discussions.microsoft.com> wrote their comments
Then Kevin replied below:
> Hi
>
> I get the following event in DNS. I tried what they said
> but the properties tab is gryed out so i can not go to
> properties. I tried to decommision the Dc but it give me
> error that says:
> Operation failed because:
> Failed finding a suitable domain controller for the
> domain
> "the specified domain either does not exist or could not
> be contacted"
>
> The problem started that we had 4 DC 2 got decomisioned
> and one stolen. The main DC was the stolen one, I wonder
> if that is the issue, Had to put DNS and Dhcp on this
> last remainig server.
>
> Please help thanks
>
> Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 414
> Date: 16/09/2004
> Time: 09:55:40 AM
> User: N/A
> Computer: GGBDC01
> Description:
> The DNS server machine currently has no DNS domain name.
> Its DNS name is a single label hostname with no domain
> (example: "host" rather than "host.microsoft.com").
>
> You might have forgotten to configure a primary DNS
> domain for the server computer. For more information, see
> either "DNS server log reference" or "To configure the
> primary DNS suffix for a client computer" in the online
> Help.
>
> While the DNS server has only a single label name, all
> zones created will have default records (SOA and NS)
> created using only this single label name for the
> server's hostname. This can lead to incorrect and failed
> referrals when clients and other DNS servers use these
> records to locate this server by name.
>
> To correct this problem:
> 1) open ControlPanel
> 2) open System applet
> 3) select NetworkIdentification tab
> 4) click the "Properties" button and enter a domain
> name or workgroup name; this name will be used as your
> DNS domain name
> 5) reboot to initialize with new domain name
>
> After reboot, the DNS server will attempt to fix up
> default records, substituting new DNS name of this
> server, for old single label name. However, you should
> review to make sure zone's SOA and NS records now
> properly use correct domain name of this server.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.

Here's what you need to do to fix it.
257623 Domain Controller's Domain Name System Suffix Does Not Match Domain
Name
http://support.microsoft.com/?id=257623


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
================================================
--
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
================================================
http://www.lonestaramerica.com/
================================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
================================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
================================================
!