CC: Pavel Simerda MIME-Version: 1.0 X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.0 In-Reply-To: <2083633114.6046783.1405694380220.JavaMail.zimbra@redhat.com> X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF30 (Linux)/8.0.6_GA_5922) Content-Type: text/plain; charset=utf-8 Message-ID: <1781981315.6059593.1405695762431.JavaMail.zimbra@redhat.com> Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) by bugs.isc.org (Postfix) with ESMTP id E7CC82D20051 for ; Fri, 18 Jul 2014 15:02:44 +0000 (UTC) Received: from mx4-phx2.redhat.com (mx4-phx2.redhat.com [209.132.183.25]) by mx.pao1.isc.org (Postfix) with ESMTP id 2B1B83493BE for ; Fri, 18 Jul 2014 15:02:42 +0000 (UTC) Received: from zmail19.collab.prod.int.phx2.redhat.com (zmail19.collab.prod.int.phx2.redhat.com [10.5.83.22]) by mx4-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s6IF2gNS026131; Fri, 18 Jul 2014 11:02:42 -0400 Delivered-To: bind-suggest@bugs.isc.org Subject: The way of binding to listen-on addresses Return-Path: Thread-Index: lsT++KRsuGV9a0K6naLha1psGUgchA== X-Original-To: bind-suggest@bugs.isc.org Date: Fri, 18 Jul 2014 11:02:42 -0400 (EDT) Thread-Topic: The way of binding to listen-on addresses X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org X-Originating-Ip: [10.5.82.12] To: bind-suggest@isc.org Content-Transfer-Encoding: 7bit From: Tomas Hozza X-RT-Original-Encoding: utf-8 Content-Length: 1686 Hi. Recently we had some issues with starting services (also named) in Fedora due to Systemd changes. This brought huge discussion about whether some services could use IP_FREEBIND socket option to be able to bind to the address, before it is configured on the interface. I looked into named sources and realized that it looks for existing interface with the specified address and if there is none it does not even try to bind to it. Did you ever considered using IP_FREEBIND socket option when binding named to a specific address(es) and changing the logic? It should be possible, but looking at the code it's far from trivial. Second think I would like to discuss is the named behavior when it is configured to listen on 'any' address. It binds to all specific addresses available on the system when starting up. If some interface goes up, one have to restart named. Did you considered adding support for netlink to be able to dynamically bind to new addresses? In Fedora we already have come "complains" [1] about why named does not bind to 0.0.0.0 when configured to listen-on 'any' address. Adam Tkac commented that he recalls the reason is that there is no portable way for IPv4 to find out to which address was the incoming packet addressed. Is this really the reason, or are there any other? Did you considered using the 0.0.0.0 address when listening on 'any' address (even to use some non-portable way on systems supporting it)? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1073038 Thank you in advance. Regards, -- Tomas Hozza Software Engineer - EMEA ENG Developer Experience PGP: 1D9F3C2D Red Hat Inc. http://cz.redhat.com