Windows Forum

Ask something
Discussion Locked

DNS problem

0 helpful
8 replies

by cchang

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have one AD DNS primary server, one win2k member as a secondary DNS server.

1st question: I get an error per hour from AD DNS primary server's event view states "Windows cannot determine the user or computer name. Returen value (5)" (event ID: 1000). I am sure the DNS configuration is correct on server. what's wrong? or it's telling me the problem on client side.

2nd question: DNS server configuration on my win2k workstation, there's no problem to access Internet no matter put AD primary, secondary or ISP DNS IPs as Preferable DNS, but my outlook's unable to send/receive email if primary or secondary DNS IP is put on the prefereable DNS. (outlook pop up for SMTP address)

8 replies

by curlergirl

The following settings on your DNS server(s) and clients should resolve any problems:

1. On your DNS servers, set up your ISP's DNS server addresses as forwarders. This way, your DNS servers will try to resolve names first and if they can't, they will forward the request to the ISP's servers.
2. Each of your DNS servers should have itself as the primary and secondary DNS server in its own (static) TCP/IP properties.
3. Each of your clients should have your internal DNS servers as primary and secondary DNS servers (can be set thru DHCP if you're using that or statically, doesn't matter).
4. If your email server is internal, make sure there is an MX record on your DNS servers for it. If not, you don't need this - your ISP's DNS will resolve the email server for you.
5. By the same token, if your email server is internal, make sure your ISP has an MX record in it's DNS for your email server.

Hope this helps!

by curlergirl

For #1 - just to further elaborate, to set up the forwarders, you go to the DNS management console on the server and go to the settings (properties) for either the server itself or the zone (I can't quite remember which).

by jayanth

Check out this explanation which I found at one of the sites...
-----------------------

Error Description: Windows cannot obtain the domain controller name for your computer network. Return value ().

Event ID: 1000

Comments: - 59 = "An unexpected network error occurred." - This may indicate a problem with the physical network (cables, fault NICs or hubs.
- 2146 = "The specified component could not be found in the configuration information."

From a newsgroup post: "Do the following to ensure that the SRV records for the AD servers are in DNS properly (from the DOS prompt):
nslookup
set type=srv
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM

You should see something like this:
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server2.YOURDOMAIN.COM
server1.YOURDOMAIN.COM internet address = 1.1.1.2
server2.YOURDOMAIN.COM nternet address = 1.1.1.1

If you don''t then you definately have a DNS problem. I would also recommend running the dcdiag and netdiag utilities on your domain controllers. If you find that the servers aren''t in DNS, then make sure dynamic updates are enabled on your DNS server and restart the netlogon server on each of your DCs.
----------------------------------------

Hope this helps you.

This discussion is closed to new replies.