nslookup showing - *** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain. Help please
Good Morning,
Thisis my question = when I type nslookup I get - *** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain".
I know naff all about DNS so please trweat me like a newbie to the subject..
On all server and work stations - however the network appears to be working.
We run a Windows 2000 system with 7 servers all on SP4, the network was install by a consultant and I am sure it's not configured properly.
I am getting Event ID 1000 - source Userenv in the event log every 2-15 mins
with a description "Windows cannot determine the user or computer name. Return value (1722)."
I have search on Eventid and come up with the following..
Value 1722 (Error code 1722) = "The RPC Server is unavailable" - Usually occurs when DNS servers are not configured properly. There is connectivity but not at the service level. See the M260371 link below for troubleshooting such issues. One note here, usually it may appear that DNS is set properly but one has to double-check all the aspects of DNS registration/resolution as the problem may not be that obvious. See also M261007 - It says that this behavior can occur if the address for the configured preferred DNS server on the client is invalid or unreachable.
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
set type=srv
_ldap._tcp.dc._msdcs.YOURD
Server: dnsserver.yourdomain.com
Address: 192.168.100.2
you should see something like this:
_ldap._tcp.dc._msdcs.YOURD
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM
_ldap._tcp.dc._msdcs.YOURD
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.
Thisis my question = when I type nslookup I get - *** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain".
I know naff all about DNS so please trweat me like a newbie to the subject..
On all server and work stations - however the network appears to be working.
We run a Windows 2000 system with 7 servers all on SP4, the network was install by a consultant and I am sure it's not configured properly.
I am getting Event ID 1000 - source Userenv in the event log every 2-15 mins
with a description "Windows cannot determine the user or computer name. Return value (1722)."
I have search on Eventid and come up with the following..
Value 1722 (Error code 1722) = "The RPC Server is unavailable" - Usually occurs when DNS servers are not configured properly. There is connectivity but not at the service level. See the M260371 link below for troubleshooting such issues. One note here, usually it may appear that DNS is set properly but one has to double-check all the aspects of DNS registration/resolution as the problem may not be that obvious. See also M261007 - It says that this behavior can occur if the address for the configured preferred DNS server on the client is invalid or unreachable.
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
set type=srv
_ldap._tcp.dc._msdcs.YOURD
Server: dnsserver.yourdomain.com
Address: 192.168.100.2
you should see something like this:
_ldap._tcp.dc._msdcs.YOURD
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM
_ldap._tcp.dc._msdcs.YOURD
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.
ASKER
Thanks Rob
That basically how we have it set up I think.
All the workstation point to one server
The 4 member server point to the same server as the workstation
The the three DC's point to themselves..
Does this sound right ?
Why would I get the message *** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain. ?
Cheers
Ian
That basically how we have it set up I think.
All the workstation point to one server
The 4 member server point to the same server as the workstation
The the three DC's point to themselves..
Does this sound right ?
Why would I get the message *** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain. ?
Cheers
Ian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok Deb - it only had a reverse lookup zone for an ip address acheme that not longer in use.
Could you explain to me what a reverse lookup zone is ?
and why nslookup won't work with out it ?
ta
Ian
Could you explain to me what a reverse lookup zone is ?
and why nslookup won't work with out it ?
ta
Ian
try this :
net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon
M.AYad
net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon
M.AYad
Hi
PAQ here:
https://www.experts-exchange.com/questions/21538591/DNS-Problems-NSlookup-non-existent-domain.html
A forward lookup zone maps names to ip addresses - so effectively you give it say, server.yourdomain.com and dns via the forward lookup zone uses the forward lookup zone to find the ip address so that it can communicate with it. The reverse lookup zone maps an ip address to a name. When you type in nslookup on your machine it looks to the ip address that you have for the dns server - which is set in tcp/ip - sends off the request to the server but it can't come back with your server name because there's no reverse zone - hence no mapping for it. Try it - delete your old ip address scheme in dns reverse lookup and then add the current one. If you use ad-integrated zones and enable dynamic updates (plus update associated pointer records on reverse zone only) on both forward and reverse zones, the servers dns is automatically updated so you don't need to worry about conflicts or out of date records should your dhcp server allocate a different ip address to a host.
Hope that helps,
Deb :)
PAQ here:
https://www.experts-exchange.com/questions/21538591/DNS-Problems-NSlookup-non-existent-domain.html
A forward lookup zone maps names to ip addresses - so effectively you give it say, server.yourdomain.com and dns via the forward lookup zone uses the forward lookup zone to find the ip address so that it can communicate with it. The reverse lookup zone maps an ip address to a name. When you type in nslookup on your machine it looks to the ip address that you have for the dns server - which is set in tcp/ip - sends off the request to the server but it can't come back with your server name because there's no reverse zone - hence no mapping for it. Try it - delete your old ip address scheme in dns reverse lookup and then add the current one. If you use ad-integrated zones and enable dynamic updates (plus update associated pointer records on reverse zone only) on both forward and reverse zones, the servers dns is automatically updated so you don't need to worry about conflicts or out of date records should your dhcp server allocate a different ip address to a host.
Hope that helps,
Deb :)
Further to your earlier post, yes, sounds OK.
I don't know that you will require reverse look up zones but "it only had a reverse lookup zone for an ip address acheme that not longer in use", could cause issues.
--Rob
I don't know that you will require reverse look up zones but "it only had a reverse lookup zone for an ip address acheme that not longer in use", could cause issues.
--Rob
For nslookup to work - you definitely need a reverse lookup zone. See the error message:
*** Can't Find server name for address <Our Perfered DNS Address> Non Existent Domain".
Reverse lookup zones map ip adresses to names - The address in the message is the ip address of preferred dns server which has been passed back to dns - the server name cannot be found because there is no reverse mapping of that ip address to a server name, which is what reverse lookup zones do. "Non existent domain" again - there's no registration in reverse dns for that ip address because there's no current reverse lookup zone. This does not mean that there are no other existing problems within dns, but this definitely explains one reason why nslookup will not work within your domain - hence this part needs resolution to facilitate any further troubleshooting that may be required.
I cannot state whether ise438 needs reverse lookup zones, but I have never used them on any LAN and nslookup works fine on all.
ASKER
Thanks again Deb - can I ask what is a "PTR record"
Ian
Ian
Debsyl99, must apologize. Read your link, and the link from that page regarding configuring DNS, and although it says in some situations it is not necessary, it is highly recommended. Guess I have just been lucky until now. I did try basic nslookup on 3 servers in 3 domains and it works on those 3 but sounds like a good preventative measure would be to add the reverse lookup zone/s. I guess only some applications require it.
The workstations should have only the server as a DNS server in the DNS settings of the TCP/IP properties. DHCP ("obtain automatically") is fine as well
The server should have only itself as a DNS server in the TCP/IP properties of the network adapter. It should be assigned a static (fixed) IP address. The ISP's (Internet Service Provider) should only be added to the forwarders in the DNS management console, under your domain controller/server. Do not add the ISP's DNS addresses to the TCP/IP properties of any network cards. If using DHCP for the workstations it is a good idea to add the server to the DNS options of the DHCP scope. Located in the DHCP management console under, server name, scope, scope options, configure scope, #006 DNS server.
See if any of that locates a problem.