non-existent domain

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
LVL 1
jdustinbAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

WeHeCommented:
Did you configure the Server itself as Primary (and only) DNS Server in TCPIP Settings?
0
jdustinbAuthor Commented:
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
WeHeCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

jdustinbAuthor Commented:
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
WeHeCommented:
"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
jdustinbAuthor Commented:
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
WeHeCommented:
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
jdustinbAuthor Commented:
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
WeHeCommented:
then sit and wait, watch eventlog and try "nslookup" later :)
0
jdustinbAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.