[prev in list] [next in list] [prev in thread] [next in thread] 

List:       maradns-list
Subject:    Re: [MARA] MaraDNS 1.1.40 released; usability issues
From:       Rich Felker <dalias () aerifal ! cx>
Date:       2005-06-10 20:59:29
Message-ID: 20050610205928.GI331 () brightrain ! aerifal ! cx
[Download RAW message or body]

On Wed, Jun 08, 2005 at 06:58:47AM +0000, sam+vh6s75g@chaosring.org wrote:
> MaraDNS 1.1.40 release.
> 
> First of all, **UPCOMING FEATURE FREEZE ANNOUNCMENT**.  On July 3, at
> 11:59 pm PST, I will no longer be adding features to MaraDNS.  At this
> point, I will enter the debug and test cycle for MaraDNS.  Requests for
> new features will be cheerfully ignored, or given a "No new features"
> form letter.  
> 
> Secondly, while I am not answering all of the messages sent to this
> list, I really appreciate people posting here and letting me know what
> their experience with using MaraDNS 1.1.x is like.  I also appreciate
> the private email I have been getting.  Since sam+vh6s75g@chaosring.org
> gets all of the spam spammers try to send to the MaraDNS mailing list
> (there is a reason you need to be subscribed to get on the list), it is
> better to send me private email to this address:
> 
> 	sam+7haxx6h@chaosring.org
> 
> First of all, I got a private email where someone is dissapointed that
> csv2 zone files do not work with the "0.0.0.0" bind address hack.  The
> reason for this is because:
> 
> * csv2 zone files need the bind address to synthesize NS records (note
>   that NS records are /not/ synthesized when specified in the zone file)
> 
> * There are problems transferring zones to BIND name servers with the
>   zone server when the bind address is "0.0.0.0"  There may be other
>   problems.
> 
> * The "0.0.0.0" bind address is no longer needed because MaraDNS now
>   has multiple IP address binding support.  Have an ipv4_bind_addresses
>   that looks like this: "127.0.0.3,10.1.2.3,10.1.2.4"

Could you please allow binding to 0.0.0.0 for those who need it? (And
just disable NS synthesis in this case.) Although they're rare, there
_are_ cases where binding to 0.0.0.0 is needed and binding to each
interface will not do. Although I don't have such a case anymore, I
used to back when I ran BIND and I had to go through painful hacking
thru its disgusting source to force it to bind to 0.0.0.0.

Rich

[prev in list] [next in list] [prev in thread] [next in thread]