I always wondered why my server was always screwed up and why Active Directory said the DNS diagnostics failed. Now I know and I would like to fix it, how do I point my domain from GoDaddy to my DNS Server? I don't have anything but an IP Address really... Its asking for 2 nameservers and additionally I can enter more but I just need this pointing to this server. How do I do that?

What does your DNS on your DC have to do with GoDaddy and websites? I think you've confused 2 different things.

Let me rephrase this, I want to use the DNS Server role in Windows Server 2003 instead of Total DNS Control on GoDaddy. How do I point it to this server? I assume it is nameservers that chooses what DNS Server to use, if its parked, if GoDaddy is hosting the DNS Server and you use it via Total DNS Control, or if you provide your own, for example I provide my own so instead of using Total DNS Control, I simply use the DNS Server role on Windows Server 2003. Well I know nothing of what nameservers to provide to route the domain to my DNS Server, I know I need to provide two and I can give more optional. Help me out setting this up please!

I'm not good with abbreviations, what does DC stand for. Sorry for my stupidity. Anyway I hope I rephrased it good for you.

You do NOT want to host your own nameserver in the sense that you mean. End of story. You've confused 2 very different things.

A DC is a Domain Controller.

Is there anyway to use this server as the DNS Server for my domain from GoDaddy? Anyway to point it to this server? I'm positive, why does it always expect me to have the DNS Server have the website and everything on the server and not have it get screwed and see it point domains to different IP Addresses and then on remote PCs pointing to the correct IP Address. Every single time I setup Active Directory it says the DNS Diagnostics failed, and this server redirects domains to different IP Addresses, while other computers see what the GoDaddy Total DNS Control says, so I can get Exchange and Sharepoint running both remote and local, of course the URLs have to be formatted differently, like entering the computer name and such, sometimes authentication doesn't work outside the internal network. The Active Directory does not work outside the internal network.

DNS is a key service for a Windows AD Domain. Without it AD just doesn't work well. It's not really designed to be doing the role your after. Im sure you could get it to do it but it wouldn't be pretty.

The diagnostics are probably failing cause the servers DNS entries are pointing to the wrong place. The server should be looking at itself or another DNS Server (On your LAN) to resolve names.

Think of Windows DNS as a record of your LAN's PCs, so they know how to find each other, rather than a record for others on the outside world to find your domains local PC's.

You should have your DHCP on your LAN pointed to your DC's DNS and let it do the resolving for the LAN. As for on the internet, you COULD do what you're talking about, but you do not want your DC exposed to the internet, and you do not want your AD DNS on the internet either.

The most common thing people do in your case is get another box, and set DNS up on it. Then on this box you only add the A records that the outside needs to know about. If you do this, then you can go to godaddy and tell them to use ns.yourdomain.com as your dns servers and you'll have to tell godaddy what its IP address its using.

An do you have a business connection, is it static? Do you have more than 1 IP address? I fail to understand how anyone that does not even understand the basics of DNS in setting up AD or for their local network, would want to host dns to the public for their website -- that has what 1 IP address, 1 host? Be it an outside host or even if hosted off your own IP.

As already stated your confusing the requirements for getting the public to the IP your website is hosted, or any other service for that matter ftp, ssh, mail, etc.. an DNS in reguards to Active Directory.

Rarely would you ever host public DNS on your DC.. As to hosting it on your own network to the public -- to be honest there would be little advantage to you doing such a thing, only issues an complications. How many hosts do you need to provide dns for?? 1 maybe 2, with what maybe a mx record? What advantage do you see to hosting this on your own machine?

In a AD setup, all machines that are members of your domain need to point to the DNS for your AD, normally in a small to medium setup this would be the DC, or multiple DCs in a bigger setup.

This is like the #1 issue people have with AD.

http://support.microsoft.com/kb/291382
Question: What are the common mistakes that are made when administrators set up DNS on network that contains a single Windows 2000 or Windows Server 2003 domain controller?

Answer: The most common mistakes are:
• The domain controller is not pointing to itself for DNS resolution on all network interfaces.
• The "." zone exists under forward lookup zones in DNS.
• Other computers on the local area network (LAN) do not point to the Windows 2000 or Windows Server 2003 DNS server for DNS.

If godaddy's total control DNS does not provide you with the dns features you need/want -- then find another DNS host.. Dyndns comes to mine, or http://www.zoneedit.com/ they provide free DNS for up to 5 domains, they even support SPF records, etc..

I maintain dns for a fortune 500 company, both the internal an external.. I am quite familiar with the working of DNS be it BIND or MS, etc. An I would never in a million years think to hosting my own dns on some soho connection. There just is no point to it!!