Hi Ursulo
You don't need the ip domain-lookup command on the switches/routers if you don't want it - it won't have any effect at all on whether your clients work.
Presuming you have your DNS servers set correctly on your client PCs, you should probably try the following steps:
1) On a client PC on a new VLAN with the problems, type nslookup. Then try entering a server name - try it on it's own (i.e. server1) and as an FQDN (server1.domain.co.uk). Record the results.
2) On your DNS server, try an NSLOOKUP same as before, but point it to itself (once in NSLOOKUP, type 'server 192.168.1.230' if it doesn't have itself as the primary DNS). Record these results.
This should confirm whether the DNS server is responding at all, and whether it is responding from the new VLAN.
A few other questions:
1) What type of client PCs do you have?
2) What DNS servers do you have assigned to the NICs on your DNS servers and DCs?
3) In your DNS management MMC, enable view/advanced features. Do you have folders containing SRV records for your DCs/GCs etc in your domain DNS zone?
Often people have misoconfigured DNS setups with AD, but don't know it because they have flat LANs and NetBIOS will resolve the names and domains via broadcast. Suddenly when they go to a routed network things stop working.
You should also have WINS configured on your network - install this service on your DNS servers, and configure all servers and clients to use the service. It's a common misonception that WINS isn't needed anymore - whilst Windows itself shouldn't need it, some applications (e.g. Outlook) require it for some functions.
Hope this helps
Aaron
Please rate helpful posts...
Aaron
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
