• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1048
  • Last Modified:

Server 2003 - DNS Forwarders..pointing to Router's Inside IP address or to ISP's DNS servers?

Server 2003 install
ISP --> Router's outside Live IP --->Router's Inside local IP (172.16.1.1)

Server 2003 has been assigned 172.16.1.21  with the 172.16.1.1 listed as the Gateway and the DNS server

I can get out and run updates etc, just fine...but my question is on the DNS forwarders....should they be pointing to that router at 172.16.1.1 for resolution....or to my ISP's DNS servers?
0
pdxsrw
Asked:
pdxsrw
  • 5
  • 2
  • 2
  • +2
4 Solutions
 
Network_Data_SupportCommented:
if you have not got a dns server then should be pointing to your ISP's
0
 
TunerMLCommented:
The good thing about the DNS Fowarders is that you can have multiple entries for redundancy, so you can have one entry pointing to your gateway (172.16.1.1, which probably will process the dns querry and forward as necessary) or if you have no other domains or ip ranges to worry about you can point straight out to the ISP's DNS Server. My personal setup is that my DNS Server forwards to my ISP's DNS Server.
0
 
pstrawserCommented:
TunerML, is it faster than pointing it to your inside router? or vlan router?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
TunerMLCommented:
It all happends so fast it's negligable I believe, but there have been a times when I did notice an improvement when going straight to the ISP.
0
 
pdxsrwAuthor Commented:
Is it a matter of preference ? What is best practice.....to have your in house DC's act as the DNS server for all..with their forwarders pointed to the ISP's DNS servers...or do you want your DC's to point to the router and have it foward the requests?
0
 
Network_Data_SupportCommented:
if you have a DNS server then all clients should point to that and then let the DNS server do the rest
0
 
pstrawserCommented:
pdxsrw,  

my suggestion to you is to point it to one of your dns server and let that handle it...  

because (cons) you have no control of that outside router, if that goes down, everyone inside your network will be down too..  anyhow, it will be faster inside the network anyway, for your network share and stuff... also, you always have control of what is going out in your network...

just point everyone to your dns server (use the dns ip as a gateway for all your workstation)

0
 
DPAITCommented:
I configure my forwarders to OPENDNS.com servers.  Gives me extra controll and I get faster DNS than through my ISP's.   I don't see how just pointing them to your router would help because it's just one more devices that has to check its settings and forward again.
0
 
pstrawserCommented:
dpait,  i use vlan that has multiple ip's  10.0.1.0 - 10.0.50.0 255.255.255.0   must connect to the vlan router and to reduse bandwith to each other..  
0
 
pstrawserCommented:
dont like the idea of using the isp as a gateway..  not much control on that side if it goes down...
0
 
DPAITCommented:
pstrawser, I understand that logic.  But where are your routers pointing?  Same issue there.  It has to get to either the DNS root servers by it's list or get it elsewhere.  I use OPENDNS because they seem to be more responsive than setting my servers to direct to the root servers, although I do have them configured to be userd if I can't get to OPENDNS.
0
 
pstrawserCommented:
update
0
 
pdxsrwAuthor Commented:
I've setup DHCP to dish out my internal server as the DNS Pri and Sec. and then set my server's forwarders to look at my ISP's DNS entries... everything is working just fine.

Thanks
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

  • 5
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now