in message : Thanks guys.
Thank you for the followup and the info. Very interesting...
: (NSLOOKUP ON 192.168.0.5 Primary)
: C:\>nslookup
: DNS request timed out. timeout was 2 seconds.
: *** Can't find server name for address 192.168.0.5: Timed
: out
: DNS request timed out. timeout was 2 seconds.
: *** Can't find server name for address 192.168.0.10:
: Timed out
: *** Default servers are not available
: Default Server: UnKnown
: Address: 192.168.0.5
: ------------------------------------------------
: (NSLOOKUP ON 192.168.0.10 Secondary)
: C:\>nslookup
: *** Can't find server name for address 192.168.0.5: Non-
: existent domain
: *** Can't find server name for address 192.168.0.10: Non-
: existent domain
: DNS request timed out. timeout was 2 seconds.
: *** Can't find server name for address 151.164.8.201:
: Timed out
: DNS request timed out.
: timeout was 2 seconds.
: *** Can't find server name for address 151.164.14.201:
: Timed out
: *** Default servers are not available
: Default Server: UnKnown
: Address: 192.168.0.5
: -------------------------------------------------
Not getting much information here. However, a lookup of the IP block
reveals SBC.
OrgName: SBC Internet Services - Southwest
OrgID: SBIS
Address: 2701 W 15th St PMB 236
City: Plano
StateProv: TX
PostalCode: 75075
Country: US
NetRange: 151.164.0.0 - 151.164.255.255
CIDR: 151.164.0.0/16
NetName: SBIS
NetHandle: NET-151-164-0-0-1
Parent: NET-151-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.SWBELL.NET
NameServer: NS2.SWBELL.NET
Something is pointing to SBC and it shouldn't.
Can you show us the ipconfig /all of 192.168.0.10 and are you in Plano? If
so, you're not that far away from me but too far to just run over and take a
look at it. (O:= I'm in Houston.
Looking at your nslookup line, it appears your primary DNS is not using it's
own or an internal one. ipconfig /all will confirm this. However, you can
put more info on the command-line rather than running nslookup and then
typing in the commands in that interface.
nslookup -q=ns rlc.org
If you're looking up a domain that you are not authoritative over, then it
will tell you non-authoritative response. If you then want to force it to
use an authoritative DNS server, you attach that to the end of it.
Ex. Since rlc.org on my end only sees the public one, this will show you
both examples but the return should be different from yours. I've blocked
out my FQDN for my DNS.
c:\>nslookup -q=ns rlc.org
Server: <censored>
Address: 192.168.0.9
Non-authoritative answer:
rlc.org nameserver = remote2.easydns.com
rlc.org nameserver = remote1.easydns.com
rlc.org nameserver = ns2.easydns.com
rlc.org nameserver = ns1.easydns.com
remote2.easydns.com internet address = 212.100.224.80
remote1.easydns.com internet address = 64.39.29.212
ns2.easydns.com internet address = 205.210.42.20
ns1.easydns.com internet address = 216.220.40.243
Now using their DNS server:
c:\>nslookup -q=ns rlc.org remote2.easydns.com
Server: remote2.easydns.com
Address: 212.100.224.80
org nameserver = TLD2.ULTRADNS.NET
org nameserver = TLD1.ULTRADNS.NET
However, if you're pointing your DNS to a server that is not correct, then
you could have mixed results and perhaps see something like what you're
seeing. I'm using MSFT as an example. First I will check for DNS servers
for the microsoft.com domain and then I'll check using a bogus microsoft.com
server which most likely doesn't have DNS running on it.
c:\>nslookup -q=ns microsoft.com
Server: <censored>
Address: 192.168.0.9
Non-authoritative answer:
microsoft.com nameserver = dns1.cp.msft.net
microsoft.com nameserver = dns1.dc.msft.net
microsoft.com nameserver = dns1.sj.msft.net
microsoft.com nameserver = dns1.tk.msft.net
microsoft.com nameserver = dns3.uk.msft.net
dns1.cp.msft.net internet address = 207.46.138.20
dns1.tk.msft.net internet address = 207.46.245.230
dns3.uk.msft.net internet address = 213.199.144.151
Ok, everything looks ok. Now, let's try the web server. (O;=
c:\>nslookup -q=ns microsoft.com
www.microsoft.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 207.46.245.156: Timed out
Server: UnKnown
Address: 207.46.245.156
Look familiar?
When you run nslookup by itself, it tries to use the primary DNS server in
your network settings. On the 2nd attempt using a bogus DNS server, it
timed out and responded with 207.46.245.156. Requesting a reverse lookup
returns:
origin2.microsoft.com [207.46.245.156]
Now, checking to see if this is the www I tried to query returns:
www2.microsoft.akadns.net [207.46.245.156]
So, perhaps we can conclude that your DNS is pointing to:
151.164.8.201 - primary
151.164.14.201 - secondary
....and not 192.168.0.5 and 192.168.0.10 as you thought. This would explain
what is happening re: your OP "Windows cannot determine the user or computer
name. Return value (1326).", because SBC doesn't know anything about your
users or your internal computers/domain. This is why you don't point to
them.
You should set all servers and workstations to point to the internal primary
DNS as primary and if you have a secondary, point the workstations and any
NON-DNS servers only to the secondary for secondary.
Remove the "." (root) entry in the forward lookup zone, if present, in the
DNS server settings.
You can add a forward, in the DNS server settings to the ISPs DNS server(s)
but it is not required. It can speed up name resolutions on the net but it
also can introduce a single point of failure. Without a forward, root hints
will be used for name resolution on the net.
If your internal DNS name rlc.org does match your external [public] DNS name
rlc.org, then you have to add entries for anything hosted externally, web
servers, email, etc. If not, no worries mate! However, in this case, you
are using a dotted DNS domain name that does have a public DNS domain name
that is not owned by you so, you will not be able to get to their web site,
www.rlc.org, should you ever want to, unless you add that entry as a host
address in your private DNS for internal users, although it might be
confusing.
Perhaps here is a question we have not asked yet. Is the DNS server service
running on 192.168.0.5 and 192.168.10?
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
2171095-LROR