Name server error issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After set up primary name server for our domain on
windows 2000 advanced server running in workgroup instead
of domain, DNS event viewer has a warning event ID 414.
It says DNS server machine currently has no domain name.
Its DNS name is a single label hostname with no domain.
("host" rather than "host.microsoft.com") This can lead
to incorrect and failed referrals when clients or other
name servers use these records to locate this server by
name. Is there workaround to fix this warning? Does the
name server have to join a domain?
 
In (e-mail address removed) <[email protected]>
wrote their comments
Then Kevin replied below:
After set up primary name server for our domain on
windows 2000 advanced server running in workgroup instead
of domain, DNS event viewer has a warning event ID 414.
It says DNS server machine currently has no domain name.
Its DNS name is a single label hostname with no domain.
("host" rather than "host.microsoft.com") This can lead
to incorrect and failed referrals when clients or other
name servers use these records to locate this server by
name. Is there workaround to fix this warning? Does the
name server have to join a domain?
Click to expand...

If you are running a workgroup you can give the machine a Primary DNS suffix
which will be added to the NetBIOS host name.
Right click on My Computer, on the Network Identification Tab you can give
the machine a Primary DNS suffix.
 
Give primary DNS suffix fix the warning ID 414. However,
when using Dig tool from geektools.com, the name server
only repond once. After that, Dig tool always say
connection time out and can not get any response from name
server. Name server is behind Cisco ADSL router, port 53
has been enabled and point to name server. I have checked
ISP and they did not block port 53 on their side. Is there
any workaround to fix it?
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
In (e-mail address removed) <[email protected]>
wrote their comments
Then Kevin replied below:
Give primary DNS suffix fix the warning ID 414. However,
when using Dig tool from geektools.com, the name server
only repond once. After that, Dig tool always say
connection time out and can not get any response from name
server. Name server is behind Cisco ADSL router, port 53
has been enabled and point to name server. I have checked
ISP and they did not block port 53 on their side. Is there
any workaround to fix it?
Click to expand...

Port 53 UDP and TCP?
You need both, especially UDP.
 
Back
Top