*** Can't find server name for address 192.168.1.101: Non-existent domain
Default Server: UnKnown
Address: 192.168.1.101
Here are my ipconfig /all results:
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : IPTMA1
Primary Dns Suffix . . . . . . . : intprotech.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : intprotech.local
INTPROTECH
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : INTPROTECH
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-0D-56-6F-CA-DE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.101.17
Primary WINS Server . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, June 03, 2005 6:25:17 AM
Lease Expires . . . . . . . . . . : Saturday, June 04, 2005 6:25:17 AM
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : INTPROTECH
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0D-56-6F-CA-DD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.101.17
Primary WINS Server . . . . . . . : 192.168.1.100
Lease Obtained. . . . . . . . . . : Friday, June 03, 2005 6:25:14 AM
Lease Expires . . . . . . . . . . : Saturday, June 04, 2005 6:25:14 AM
here is my reverse lookup zone data:
Name Type Status
0.in-addr.arpa Standard Primary Running
127.in-addr.arpa Standard Primary Running
255.in-addr.arpa Standard Primary Running
1.168.192.in-addr.arpa Active Directory-Integrated Primary Running
the first three were created automatically "i think"
I created the last one per "troubleshooting nslookup.exe" on ms support web
site
I must add that everything is in working order every test i do passes i can
ping both IP addresses plus the host IPTMA1. AD is in working order. I cannot
find any thing wrong with the setup accept for the PTR record? not sure if it
is correct?
Basically Is this nslookup error a major problem? will i be able to install
ms exchange without problems?
Thank you, Is there is any more information I can give to help?
I will give you my version, but please note that I am far from being an
expert. If you act on what I say please investigate it thoroughly
first!
The nslookup is normal if you don't have a ptr record associated with
the zone.
In your case the below might explain why you get a similar result.
You have your Isp server listed in the Ipconfig /all. This is wrong and
only the internal dns server should be configured there throughout the
whole domain. (Including your clients!). As at a guess I would say that
this is your Domain controller or internal dns server. You have the
following occuring that the dns server does not even query itself for
resolution. Only the Isp. That explains why you see the nslookup
result. (I am mildly qurious why it shows any intenal adress at all?) I
would guess the reason why AD "works" is because of netbios/wins. (you
could try to login in with the following format: x...@intprotech.local
this will force a dns name resolution for the srv records. Even do if
it does work, there is still a big chance that the rest of the domain
uses netbios, because if the name resolution for an internet siet came
only once from your isp server. It will keep going there and not to the
internal dns server.)
You also seem to have a multihome DC/Dns server. This is a problem, you
should look at.
john
Thank you for your time
You need to take my my advice first, the DC has a 0% chance of registering
in your ISP's DNS servers.
It must be using a DNS server that supports the AD Domain, and dyanamic
registration. It is recommended for the DC to use DNS on itself. For that to
happen it must have a static IP address.
I'd bridge these connections, assign them a statice IP address, and use that
static IP address as the only DNS server in TCP/IP properties. It is better
to have only one DNS server in the list, as long as it supports the AD
domain, than to have any DNS server that does not support the AD Domain in
any position.
Thank you very much - I found another post of yours to resolve other issues
and they also worked without hiccup.