DNS Problem

Do all of your client PC's point to the local (Win2k8) servers?

yes they do.

from a command prompt (on the client) type this:

c:\> nslookup servername

and copy/paste back the results. That will probably tell us a lot.

C:\>nslookup ourdcsrvr
Server:  UnKnown
Address:  192.168.19.46

*** UnKnown can't find ourdcsrvr: Server failed

C:\>

is 192.168.19.46 the DNS server? Is the zone defined in the DNS server?  

is 192.168.19.46 the DNS server?
Yes

Is the zone defined in the DNS server?
not sure what you mean?

When you set up the DNS server, did you define your local zone? You need a local DNS zone to identify your local domain.


http://technet.microsoft.com/en-us/network/bb629410.aspx

There are 3 zones under "forward lookup zones" that end in .loc

Is this what you are referring to?

I don't think so. You actually need to create a zone for Microsoft DNS to work on your network to ID your servers.

If this is a forwarding zone and it's typically named with the mydomain.loc, then I have this.   I can't answer your question authoritatively because I'm only vaguely familiar with DNS setup and didn't set this one up.  I believe it was setup wrong but can't begin to tell you how it's wrong.  Is there some other clue to this "local zone" that will tell you/me that it's setup?  Can you tell me more??

can you do an nslookup on myserver.mydomain.loc?
If so, then add mydomain.loc to the dns suffix on the workstation and see if you can nslookup myserver.

In the forwarding zone, is there a SOA defined?

Please post a screenshot of your DNS console with your zones. Also, post ipconfig /all

I may have inked over too much....    let me know and i will paste another version
ipconfig-capture.jpg
DNS-screenshot.jpg

Did you post ipconfig /all for the server or a client? Please do the server as well and post.

First issue is that you have a DNS Suffix that doesn't match your domain called Mshome.net.

Disable IPv6 run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.

What is the second DNS zone listed?

There have been some problems with the msdcs zone being delegated. You need to manually update you SRV records in the msdcs.domain.com zone or you can delete both your domain.com and msdcs.domain.com zone and re-create it as one domain.com zone.

Hi Dariusq,

I will post the ipconfig soon - i've been swamped. The DNS started working again internally after removing references to the old domain.  There are still some problems though.  Even if it appears to be working.  

You say "disable ipv6".   i'm inclined to do so if it makes it run better - can you elaborate on this?
Thanks

If your other network clients don't have IPv6 they can have trouble communicating with each other inlcuding the IPv6 address causing DNS resolution issues.

dumb question, I didn't setup this network, if I disable the ipv6 on the DNS server, what are possible "unintended consequences"?

My logic tells me that both ipv4 and ipv6 are operating and when ipv6 goes away, everything will fall back to their respective ipv4 addresses....   Do you have any thoughts on this? I don't want to interrupt production.

You won't cause any network communication problems if you disable IPv6. Do you have Exchange running on this box?

Here is the Ipconfig from the DNS server
IPConfig-capture.txt

IPv6 has been disabled.