Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
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!
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!
Asked:
2-
2
- +1
2 Solutions
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.
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?
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?
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.
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.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
DNS forwarder:
http://technet.microsoft.com/en-us/library/cc754941.aspx