Basic Networking DNS Question

Howdy Experts:

Just inherited a 4 server setup -- 1 DC (2008 R2), 1 Terminal Server, 1 App server and 1 SQL server.  Only the DC has an outside IP address, plus and inside (192.168.1.50).  The other servers are all addressed locally, 192.168.1.110 - 112.  The Router address is 192.168.1.1.

My question -- this was previously set up so the three inside servers had a DNS 1 pointing to the router (192.x.x.1) and DNS 2 pointing to the DC,  which is hosting DNS (192.x.x.50).  In the past, I would only use DNS1 pointing to the router on all servers and workstations -- is there an advantage to setting up my DNS to read both IP addresses?   If so, what order?

Thanks!
TetonWestAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
jramsierConnect With a Mentor Commented:
I would have them all pointing to the DNS server then the router (2nd DNS to router is debatable).  Then on the DNS server have a dns forwarders set to googles DNS (8.8.8.8 and 8.8.4.4), your ISP's DNS, or another.  

DNS forwarder:
http://technet.microsoft.com/en-us/library/cc754941.aspx
0
 
BillBondoCommented:
You would think the router would have the outside address, acting like a gateway.  What kind of router? I would just use the DC for DNS.
0
 
TetonWestAuthor Commented:
Thanks for the comments guys -- Bill I was using the word router and meant gateway.  Our gateway has the leased IP plus outside DNS servers on the WAN and 192.168.1.1 for the LAN.  

JR -- am i right in saying you think I should have my workstation and servers point to the inside address of the DC hosting DNS rather than pointing it to the GW?
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
QlemoConnect With a Mentor DeveloperCommented:
Windows does not use the second DNS server, unless the first does not respond at all. If the first DNS server is the router, and if it fails no Internet connection will be available. A secondary DNS does not make sense (in regard of Internet).

In a Domain you should always use a DC as DNS server. This also has the advantage that the DC can act as a DNS proxy, caching resolved names. In that setup the secondary DNS might be the router, to still allow for (delayed) DNS resolution of Internet addresses even if the DC is offline for some reason. If another DC were available, I would use that as secondary DNS.
0
 
jramsierCommented:
Yes you are correct , I would test it before going live with the settings changes through.  I have seen some techs make some wierd settings for a specific reason and if you change them all, they all might be broken can cause more issues, although you are tring to fix it.
0
 
TetonWestAuthor Commented:
Thanks everyone!
0
All Courses

From novice to tech pro — start learning today.