[sf-lug] resolver problem

[Alex Kleider]

Sounds like a good topic for a Linux meeting: tomorrow at NoiseBridge perhaps &/or at the next SF-LUG ?
I'd be happy to share with you my experiences.  I have kept notes- including distillations of what Rick posted when this came up a few years ago.


a_kleider at yahoo.com

--- On Mon, 8/27/12, jim <jim at systemateka.com> wrote:

From: jim <jim at systemateka.com>
Subject: Re: [sf-lug] resolver problem
To: "Rick Moen" <rick at linuxmafia.com>
Cc: sf-lug at linuxmafia.com
Date: Monday, August 27, 2012, 12:47 PM



    (Maybe things have changed since last I looked.) 
    I've spent time, occasionally, looking through pages 
of search engine results and other sources trying to 
learn how to set up a DNS server. There's lots of info, 
but what I've seen does not give me what I need to do 
the job. There are lots of concepts, but they don't 
relate to creating the proper files. There are tutorials, 
but they are specific to particular problems that are 
not a simple, general purpose DNS resolving system. 
    What I'd like to know is what software to get and 
what configuration files to create on the server side 
so that a client request to resolve a domain name gets 
access to the requested server. If necessary, what 
client-side configuration files to create to access my 
home-brewed DNS server. 
    I believe it's easy to do if one knows what to do. 





On Mon, 2012-08-27 at 11:06 -0700, Rick Moen wrote:
> Quoting Alex Kleider (a_kleider at yahoo.com):
> 
> > Daniel G was kind enough to spend a lot of time with me at last
> > Monday's LUG meeting trouble shooting this problem.  In the end he
> > concluded that for reasons never made clear, resolver requests were
> > being sent out using TCP instead of UDP and some servers honored that
> > and some stuck to the rules and did not.  Changing /etc/resolv.conf
> > to point to a server that did seemed to solve the problem (or should I
> > say, 'circumvent' the problem, if that is indeed what it was. I can no
> > longer reproduce the problem so can not investigate further.)
> 
> Yes, but why outsource DNS at all, in the first place?
> 
> You can run a full-service recursive nameserver of your own on just
> about anything, it completely avoids problems such as the one you 
> cite above, it doesnt't take much in the way of machine resources, and 
> it pretty much runs itself.  (There's nothing really requiring
> administration.)
> 
> I can understand people wanting to outsource their authoritative DNS on
> grounds of administrative headache (though I do not concur), but
> outsourcing recursive DNS seems a bit silly.
> 
> (Software?  Your choice of Unbound, PowerDNS Recursor, BIND9, Deadwood,
> dnscache.)
> 
> 
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/



_______________________________________________
sf-lug mailing list
sf-lug at linuxmafia.com
http://linuxmafia.com/mailman/listinfo/sf-lug
Information about SF-LUG is at http://www.sf-lug.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20120828/219488df/attachment.html>