Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

nslookup non-existent domain

0 views
Skip to first unread message

speedracer

unread,
Jun 3, 2005, 12:09:02 PM6/3/05
to
I have been trying to fix a already running window server 2003 system because
i need to install ms exchange. I cannot resolve this dns ns lookup problem

*** 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?

jacks...@hotmail.com

unread,
Jun 5, 2005, 5:49:16 AM6/5/05
to
Hi there,

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

Kevin D. Goodknecht Sr. [MVP]

unread,
Jun 5, 2005, 11:14:38 AM6/5/05
to
> I have been trying to fix a already running window server 2003 system
> because i need to install ms exchange. I cannot resolve this dns ns
> lookup problem
>
> *** 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<--remove

>    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>    Ethernet #2 Physical Address. . . . . . . . . : 00-0D-56-6F-CA-DE
>    DHCP Enabled. . . . . . . . . . . : Yes<--DCs with DNS must be static

>    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<--don't use these
>                                        216.41.101.17<--don't use these

>    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<--remove

>    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>    Ethernet Physical Address. . . . . . . . . : 00-0D-56-6F-CA-DD
>    DHCP Enabled. . . . . . . . . . . : Yes<--DCs with DNS must be static

>    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<--don't use these
>                                        216.41.101.17<--don't use these

>    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?

Since both NICs are on the same subnet you should bridge these two NICs so they only have one IP. Then assign the bridge a static IP address and use that address for DNS on this server and all member clients. Remove the Single-label DNS suffix from the DNS tab of TCP/IP properties. Run netdiag /fix and netdiag /test:dns /v and look for errors. You can verify Active Directory is working properly with dcdiag /v.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

speedracer

unread,
Jun 16, 2005, 2:15:07 PM6/16/05
to
Thank you for your posts they have been helpful, I have been trying to change
this server while employees are working and between the 3d modeling projects
i have. so i have finally gotten netdiag to work after getting the right one
and it's main problem i think is that my domain controller is not registered
in DNS. I am looking for the way to change that now. also i have realized
that outside of the office my web page does not come up it says cannot find
dns server so i think this is the same problem with the DC. I am working on
these problems now and after that i will take your advice and bridge my nic
cards. I will post back when this is complete.

Thank you for your time

speedracer

unread,
Jun 16, 2005, 6:11:05 PM6/16/05
to
I have been trying to fix this server in between my 3d modeling projects and
while employees are working so it's going very slow, but I have installed the
correct netdiag from the win server 2003 disc and it looks like my main
problem is that my DC is not registered in my DNS, I am looking for ways to
resolve this now. After the DC is registered I will take your advice and
bridge my two nic's together.

Kevin D. Goodknecht Sr. [MVP]

unread,
Jun 17, 2005, 4:53:56 AM6/17/05
to
In news:46CB298F-C368-4037...@microsoft.com,
speedracer <speed...@discussions.microsoft.com> posted this:

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.

speedracer

unread,
Jul 6, 2005, 1:49:05 PM7/6/05
to
Thank you for your time and support - It is running like a champ.

Thank you very much - I found another post of yours to resolve other issues
and they also worked without hiccup.

0 new messages