Public DNS

[John Miller]

Short answer: don't!  Running a public recursive DNS server is an
incredibly bad idea unless you have the resources of Google or other
ISPs.  It's easy for attackers to exploit it in several ways, and
you'd also need to solve some non-trivial load balancing and caching
challenges.  There's way more to it than just setting up BIND and
letting fly.

If you're looking to set up a recursive DNS server for yourself or
your organization, I'd suggest starting by reading DNS and BIND, 5th
edition, by Paul Albitz and Cricket Liu (O'Reilly).  Great
introduction to DNS in general as well as BIND configuration.  Start
there, experiment around a bit with some sandbox vms, then come back
here when you've got some more specific questions.

John
-- 
John Miller
Systems Engineer
Brandeis University
johnmill at brandeis.edu


On Thu, Apr 2, 2015 at 9:25 AM, Heamnath J <heamuj at gmail.com> wrote:
> Hi
>
> How to configure a DNS server as public DNS server like google's 8.8.8.8 server
> Help me to clear out these problem
>
> Thank you
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users