Windows DNS Server

Hi!

We have a small network with a windows2000server and differente
Win2000pro and winXPpro as clients in a domain. I would like to set the
PDC as DNS server, too. I've configured the dns server (and client) set
up the zones but on the clients, every time i do a nslookup i got this
message:

C:\>nslookup [dns name here]
*** Can't find server name for address [ip of our PDC]:
Non-existent domain

Where am i wrong?
--
Pascal Brax
BOFH / SysAdmin
"To play like an angel you should first work like a devil"
removethisfakedomain to mail me.

You cannot have a Windows 2000 domain controller without running DNS. Where
was the DNS server before?

"Pascal Brax" <pascalbrax@freesurf.removethisfakedomain.ch> wrote in message
news:eVj0VeYPEHA.1512@TK2MSFTNGP10.phx.gbl...
> Hi!
>
> We have a small network with a windows2000server and differente
> Win2000pro and winXPpro as clients in a domain. I would like to set the
> PDC as DNS server, too. I've configured the dns server (and client) set
> up the zones but on the clients, every time i do a nslookup i got this
> message:
>
> C:\>nslookup [dns name here]
> *** Can't find server name for address [ip of our PDC]:
> Non-existent domain
>
> Where am i wrong?
> --
> Pascal Brax
> BOFH / SysAdmin
> "To play like an angel you should first work like a devil"
> removethisfakedomain to mail me.
>

"Pascal Brax" <pascalbrax@freesurf.removethisfakedomain.ch> wrote in message
news:eVj0VeYPEHA.1512@TK2MSFTNGP10.phx.gbl...
> Hi!
>
> We have a small network with a windows2000server and differente
> Win2000pro and winXPpro as clients in a domain. I would like to set the
> PDC as DNS server, too. I've configured the dns server (and client) set
> up the zones but on the clients, every time i do a nslookup i got this
> message:
>
> C:\>nslookup [dns name here]
> *** Can't find server name for address [ip of our PDC]:
> Non-existent domain
>
> Where am i wrong?
> --
> Pascal Brax
> BOFH / SysAdmin
> "To play like an angel you should first work like a devil"
> removethisfakedomain to mail me.
>


The first thing NSLOOKUP tries to do is to do REVERSE dns lookup
on the IP address of the DNS server, to give the DNS server name.

All this error means is that the reverse lookup zone for your subnet has not
been set up, or does not contain a PTR record for the DNS server machine.

Whilst not having reverse DNS set up would be
considered a bit sloppy, it's not fatal.

NSLOOKUP should be able to do normal forward
lookups on names on this server anyway. Can it?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking