DNS server Unknown

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

when I run nslookup I receive the following ***Can't find
servername for address 192.168.7.2:Non-existant domain***
Default servers are not available
Default Server: Unknown
Address: 192.168.7.2

Where my domain is ESHINC.local and the server address is
192.168.7.2 and is also the DC. My problem is that the
computer name is ESH.ESH-SERVER.chartertn.net. I keep
getting a 5782 netlogon warning in event viewer:Dynamic
registration or deregistration of one or more DNS records
failed with the following error:
No DNS servers configured for local system. The real
problem is that the client computers are timing out while
browsing shared folders on the server. What is my best
plan of corrective action?
 
In
Jason said:
when I run nslookup I receive the following ***Can't find
servername for address 192.168.7.2:Non-existant domain***
Default servers are not available
Default Server: Unknown
Address: 192.168.7.2
Click to expand...

This is an error produced by nslookup when it tries to perform a reverse
lookup on the DNS server it is pointing to. You can ignore this or create a
reverse lookup in the DNS server for your private subnet.
Where my domain is ESHINC.local and the server address is
192.168.7.2 and is also the DC. My problem is that the
computer name is ESH.ESH-SERVER.chartertn.net. I keep
getting a 5782 netlogon warning in event viewer:Dynamic
registration or deregistration of one or more DNS records
failed with the following error:
No DNS servers configured for local system. The real
problem is that the client computers are timing out while
browsing shared folders on the server. What is my best
plan of corrective action?
Click to expand...
If your domain is ESHINC.local and the Full computer name is
ESH.ESH-SERVER.chartertn.net then you have a disjointed namespace which will
produce a 5782 event.
I would need to see an ipconfig /all and a verification of your actual
domain name in ADUC to advise corrective action.
You may be able to fix this with a script that can be obtained from MS
Customer support if it is only the Primary DNS suffix that is incorrect.
 
Thanks for your response:
Here is the Ipconfig /all info:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : ESH
Primary DNS Suffix . . . . . . . : ESH-
SERVER.chartertn.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ESH-
SERVER.chartertn.net
chartertn.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R)
PRO/100+ Server Adapter (PI
LA8470B) #2
Physical Address. . . . . . . . . : 00-02-B3-88-
70-8D
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.7.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.7.20
DNS Servers . . . . . . . . . . . : 192.168.7.2
Primary WINS Server . . . . . . . : 192.168.7.2

AND the verified domain name in ADUC is ESHINC.local
 
In
Jason said:
Thanks for your response:
Here is the Ipconfig /all info:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : ESH
Primary DNS Suffix . . . . . . . : ESH-
SERVER.chartertn.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ESH-
SERVER.chartertn.net
chartertn.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R)
PRO/100+ Server Adapter (PI
LA8470B) #2
Physical Address. . . . . . . . . : 00-02-B3-88-
70-8D
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.7.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.7.20
DNS Servers . . . . . . . . . . . : 192.168.7.2
Primary WINS Server . . . . . . . : 192.168.7.2

AND the verified domain name in ADUC is ESHINC.local
Click to expand...
Jason,
Yes, this is a disjointed namespace that is the reson for the 5782s If you
will contact me directly by email I may be able to help you with fixxing
this.
There are also other minor problems with this config such as your DNS Suffix
search list.
You actually only need ESHINC.local in your list since that is your local
DNS domain name, having the extra names in the search list can cause slow
resolution and with Verisign's supreme wisdom to add a wildcard record the
extra names will cause you problems. This has been under close scrutiny in
the NG for the last couple of weeks because just about any name you put in
will resolve to 64.94.110.11.
 
In
Jason said:
Kevin,
I tried to email yopu at (e-mail address removed) but it
bounced!?
Click to expand...
You must remove the nospam. from my email address.
 
J> when I run nslookup I receive the following ***Can't find
J> servername for address 192.168.7.2:Non-existant domain***
J> Default servers are not available

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-message.html>

That is unrelated to either your problem or your real problem.

J> My problem is that the computer name is
J> ESH.ESH-SERVER.chartertn.net.

That's only a problem if you haven't set up "split horizon"
DNS service (since that domain name doesn't exist in the public
DNS database).

J> The real problem is that the client computers are timing
J> out while browsing shared folders on the server.

That could be a wide range of things. What, exactly, are you
doing when the timeout occurs ? What does the error say ?
 
In
Jonathan de Boyne Pollard said:
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-m
essage.html>

That is unrelated to either your problem or your real problem.


That's only a problem if you haven't set up "split horizon"
DNS service (since that domain name doesn't exist in the public
DNS database).


That could be a wide range of things. What, exactly, are you
doing when the timeout occurs ? What does the error say ?
Click to expand...

If you had read through the thread then you would know Jason's real problem
was his disjointed namespace.
 
J> The real problem is that the client computers are timing
J> out while browsing shared folders on the server.

JdeBP> That could be a wide range of things. What, exactly, are
JdeBP> you doing when the timeout occurs ? What does the error say ?

KDGS> If you had read through the thread then you would know Jason's
KDGS> real problem was his disjointed namespace.

Wrong. If I had seen your message before composing my reply (Please try
not to assume that everyone in the world receives Usenet messages at the
same time and in the same order as you do.) I would have merely seen you
concentrating on just one of the things that he mentioned and ignoring the
other. However, in this case one only actually needs to have read the
original post to know what his real problem was, since in it he clearly
stated (as can be seen above) what his real problem was, even using the
words "real problem" to describe it as such.
 
In Jonathan de Boyne Pollard
<[email protected]> posted their
concerns
Then Kevin made his reply below:
try not to assume that everyone in the world receives Usenet messages
at the same time and in the same order as you do.)
Click to expand...

If it takes two or three days for these messages to reach the news server
you are using then maybe you should consider using a different news server
as I have had to do this week while the MS Newsgroups have been under the
swen worm attack.
 
Back
Top