SUFFIX in name resolution (DNS - Win Srv 2003) in NON-domain context

[999364]

Hi,

I have always worked with DNS (Windows Server 2003/2000) with domain/s-forest/s.
So Configuring DNS in this context it is a little bit different form configure it in a NON-Domain environment.

My Question Is:

I Installed DNS on Windows server 2003 in a NON domain environment (so NO forests, domains and AD just to be clear).

I setup the primary zones and reverse ones, everything looks like working, forwarding with internet is OK (Web Site are browsable), but there is thing:

I had to add a suffix (the name of the zone) in the TCP/IP address setting of client to resolve names:

e.g.: suppose the zone is called myzone,
clients are Cl1, cl2 and so on.

If I run nslookup from a client, my DNSserver is recognised, but to solve the names I have to append a suffix:
CL1.myzone, cl2.myzone.
Without the suffix, names (machines) do not exist.

So my question is:

How to setup DNS and zones to avoid to add suffix in TCP/IP settings.

Thanks

 

[999364]

Anyone could give me a suggestion?

thank

 

[lgarner]

DHCP can put that in for you.

 

[GlenJohnson]

Maybe a good old fashioned hosts file would help? Just a thought.

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum

 

[999364]

I know to use host file, but I would like to avoid it, just to use dns.

About DHCP I will try it