DNS Config issues 1

[Trekk]

I am trying to to setup a Windows 2003 DNS Server Non Active Directory Primary Server
Here is my confusion
I have an old Unix DNS with the IP address of 192.1.1.3 it is working right now and all my users are resolving to it. My users have address of 192.168.1.1
But the powers to be want me install DNS on a Windows 2003 Server and give it the same address as the old one because we are removing UNIX from our network and we don’t want to change all the IP’s on the routers\switches that already have the 192.1.1.3 address.

I created a forward look zone with mycompany.com and 2 reverse lookup zones for 192.1.1.1 and 192.168.1.1

When I try to do an nslookup .For example a server on our network I get can’t find server (server. name) Server failed. But if I use the FQDN it works just fine.
On the old server 192.1.1.3 it resolves a plain host (server) name to a FQDN

What I am afraid of is that when I put this new DNS in and replace the old one there will be issues in resolving DNS queries

What am I missing?

Thanks

 

[jyorgey]

The problem is not with DNS but with your client that is querying the DNS server. Your new DNS server is responding correctly to the question. DNS servers will only answer queries that are fully qualified. It is the job of you client machine to add the domain to the end of your query to fully qualify it. Check that you have added the new forward domain to you suffix search order in TCP/IP stack.

You can check to see what the query looks like going to your DNS server in nslookup by putting it in debug. You can set nslookup in debug by typing “set d2”. This will allow you to see the question you are asking the DNS server.

 

[Trekk]

Thank you
That was it, I now feel like an idiot
I guess I got to wrapped up in the cofiguration of the DNS to have any common sense