Proper DNS Settings on DHCP Server on Domain

You must point your DNS server to itself. As far as setting up the DHCP server, you'd set the NIC settings up the same as you would any other computer on your domain. I hope this helps.

So.. first.  DHCP in itself doesn't provide access to the Internet.  It simply gives the DHCP client the information it has for DNS, etc.. If you are hosting your own DNS (you don't have to) then the DNS server provides translations from host names to ip addresses.

Your question is really loaded, but here goes.

If you choose to set up your own DNS, then the DHCP server should have the 192.168.1.1 address as the DNS server.  You would then set up DNS Forwarders in the DNS applet using the ISP DNS server ip addresses.  You set these by opening up the DNS management applet right click on the main DNS serverm click on the Forwarders tab and enter them there.

If you are NOT hosting your own DNS, then the DHCP server should have the 76.85.229.110 and 76.85.229.111 ip addresses as the DNS server.

Hope that helps.

KaptainKenbo:

I am hosting DNS myself but it is for a DC so is it useable for internet traffic as well as LAN traffic?

And should I list my ISP DNS's as 2nd and 3rd options in DHCP?

Should I list my routers IP as a DNS Server I dont even know if it works as DNS as well as everything else? I would guess not.

BTW I fully understand DHCP thanks for the extra explaination

KaptainKenbo:

I am running Server 2008.

How do I setup the forwarders?

Thanks so much for your help.
Stuart

I got it right click DNS in DNS Server console select properties and then click the forwarders Tab.

Thanks again.

It may take a little while for everything to take effect.  You may have to have the client machines reboot and maybe even ipconfig /flushdns.

Ok thanks I'll keep that in mind.

KaptainKenbo:

When I set my DNS settins and DHCP Settings to what you recommended I lost reliable internet access.

It became rare for me to connect to a website.

When you say you lost "reliable" internet access do you mean that it was intermittent?  

With the setup that I provided, if you ping www.getfirefox.com, what do you get?

What happens if you ping 63.245.209.24?

Something has to be wrong on the setup.  This is the way it should be done if you want to run your DNS server and have it handle both internal and external DNS requests.  

I mean the internet is down more than its up.

I cant reconfigure anything right now since its actually working decently and dont want to mess it up.

So I'm unable to test it right now

What you explained to me sounded resonable and correct but I got really bad results.

I wonder if I'm having an issue with DNS at 192.168.1.1 and thats why the only way I can get funtctional DNS for internet is to include my ISP DNS servers as 2nd and 3rd on my DHCP setup?

Read https://www.experts-exchange.com/questions/24155319/Random-disconnects-from-the-server.html

I am having new issues now.

Can you expand all of the options on your DNS applet and attach that on a message here?

Also are you getting any event log messages on DNS?

here is a log of the errors
DNS-Log.txt

sorry csv not cvs

I dont know if this will do you any good but AD and DNS are linked so I thought I would list this one as well. Again its a csv file.
AD-Log.txt

Attached is a JPG of DNS Tree
DNS.jpg

Here is DHCP
DHCP-Scope-Options.jpg

BTW with DHCP set like this it at least works if I take off the the ISP DNS servers it completely dies on me or at least close to completely.

And here are my forwarders. BTW it already had the 2 on the bottom I guess it somehow resolved them on its own with out me inputing them. And I added the 2 on top.
Forwarders.jpg

Sorry I was backwards I added the 2 bottom ones not the top.

Not that you really need it but just to verify my settings heres my ISP info
Router.JPG

It looks like you have conditional forwarders set up in the DNS tree.  What are your conditional forwarders?  I've never seen forwarders "just appear" in the forwarder's tab, so that's a little weird.

Hopefully that gives you some idea of my setup if you need anything else let me know.

BTW things seem to be semi reliable since I added my ISP DNS back in But right now I have Offline Files disabled on the client since this causes it to disconnect.

Thanks for all your help

I dont even know what conditional forwarders are and like I said 66.xxx.xxx.xxx ips in there were there when I first saw this tab. In other words I didn't enter them. I did enter the others though.

Conditional forwarders are set up in the DNS applet.  Expand the tree, they are located adjacent to Reverse Lookup Zones.

Cripes.. all this time I thought we were looking at a Windows 2003 server problem.  Then I noticed that you have both Windows 2003 AND 2008 in the categories of the issue.

yeah that was because I migrated from 2003 to 2008 and thought that my migration might have been where I messed things up.

Ok, so I'm assuming you didn't set up the original 2003 server, because those DNS entries in the forwarders tab should not have just appeared there.  They are probably left over from the 2003 migration.  

Anyway, did you take a look at the Conditional Forwarders leaf in the DNS applet?

Is this what you were talking about because in this view it doesn't list anything
Conditional-Forwareders.jpg

As far as I know I didn't migrate DNS only AD.

Yeah when I demoted the 2003 server I still had to go in and remove the DNS Role so I'm guessing that dcpromo on the 2008 server would have just installed the normal DNS Server not migrated it.

Dont really know.

And Yes I did configure the Server 2003 machine initially and maintained it as well. And I knew nothing about Forwarders let alone Conditional Forwarders

Ok, well, since you are using a LinkSys router and not the Windows 2003 server itself, I would just do this to keep things simple.  It appears as if you don't need a complicated setup.

If it were me at this point, I would go in and remove the DNS role completely on the 2008 server and then go in and add it again using the wizard provided.  Here is a reasonably good article with pictures on how to do it.

http://blogs.techrepublic.com.com/datacenter/?p=327

I am sure the migration thing didn't help matters.  I don't like doing migrations.  I like to build the server and bring on roles one at a time until I have basically the old server duplcated on a subnet and then change the IP addresses when I bring it into production.

Anyway, thanks for the points.  Good luck with getting it all set up.

Thank you for all your extra help.