?
Solved

non-existent domain

Posted on 2004-11-27
10
Medium Priority
?
537 Views
Last Modified: 2006-11-17
Just recently installed windows server 2003 standard with DHCP, DNS, and set it as a Domain Controller. I am extremely NEW to this stuff so my knowledge is rather limited.

Upon doing nslookup on the server I get non-existent domain.

Where to go from here? Please let me know if you need any additional information.

Thanks!
jd
0
Comment
Question by:jdustinb
  • 5
  • 5
10 Comments
 
LVL 11

Expert Comment

by:WeHe
ID: 12687857
Did you configure the Server itself as Primary (and only) DNS Server in TCPIP Settings?
0
 
LVL 1

Author Comment

by:jdustinb
ID: 12687880
TCP/IP settings have the server listed as the Preferred DNS server.

I then have my ISP's DNS servers listed as the next two.

Able to do an nslookup for google and such.

C:\Documents and Settings\admin.server>nslookup www.google.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
Server:  UnKnown
Address:  192.168.0.1

Non-authoritative answer:
Name:    www.google.akadns.net
Addresses:  216.239.57.104, 216.239.57.147, 216.239.57.103, 216.239.57.99
Aliases:  www.google.com

0
 
LVL 11

Accepted Solution

by:
WeHe earned 2000 total points
ID: 12687948
1) Noother DNS servers as the server itself MUST be configured.
2) ISP DNS Servers have to be configured as forwarders in DNS Server Properties, not as secondary dns.
3) "*** Can't find server name for address 192.168.0.1: Non-existent domain" means, you have no reverse lookup zone in DNS for your IP addresses.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Author Comment

by:jdustinb
ID: 12688057
ok so I removed the ISP's DNS Servers and placed them under the DNS server forward queries.

Now when configuring DNS Server, it says creating a forward lookup zone is recommended for small networks whereas forward and reverse is recommended for large networks.

Despite the fact that there are only about 10 clients that will be connecting to this server, I still need to create a reverse lookup zone?

In doing so, I am assuming I want a primary zone but how do I want this replicated? Default is to all domain controllers in the active directory domain home.local? And then there is the Network ID which is where I become completely lost.

0
 
LVL 11

Expert Comment

by:WeHe
ID: 12688133
"Now when configuring DNS Server, it says creating a forward lookup zone is recommended for small networks whereas forward and reverse is recommended for large networks.
Despite the fact that there are only about 10 clients that will be connecting to this server, I still need to create a reverse lookup zone?"

yes, it's allways good to have a acurate reverse zone. it does not depend on the size of your net.

"In doing so, I am assuming I want a primary zone but how do I want this replicated? Default is to all domain controllers in the active directory domain home.local? And then there is the Network ID which is where I become completely lost."
Create it as a AD Integrated Zone.
To all DC's in the AD Domain home.local.
Network ID depends on your IP Addresses. In your case 192.168.0 if you use netmask 255.255.255.0
0
 
LVL 1

Author Comment

by:jdustinb
ID: 12688164
Options that it gave me were primary, secondary, and stub and then there's a check box if I want to store the zone in AD.

Selected primary with the check box marked. Still getting same message with nslookup...restarting real fast.
0
 
LVL 11

Expert Comment

by:WeHe
ID: 12688193
now do a "ipconfig /registerdns" on all dc's.
at a minimum it should be done on 192.168.0.1.
after that, they should register in the reverse zone.
0
 
LVL 1

Author Comment

by:jdustinb
ID: 12688258
Told me that registration of the DNS resource records for all adapters of this computer has been initiated. any errors will be reported in the even viewer in 15 minutes.

0
 
LVL 11

Expert Comment

by:WeHe
ID: 12688313
then sit and wait, watch eventlog and try "nslookup" later :)
0
 
LVL 1

Author Comment

by:jdustinb
ID: 12688322
C:\Documents and Settings\Administrator.BACKBONE>nslookup
Default Server:  server.home.local
Address:  192.168.0.1

Is a big woo hoo in order?
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Learn about cloud computing and its benefits for small business owners.
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question