From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: make local zone transparent
Date: Tue, 28 Apr 2020 09:13:27 +0300 [thread overview]
Message-ID: <20200428061327.GA19346@tarvainen.info> (raw)
In-Reply-To: =?utf-8?q?=3CAM0PR03MB605172FBC34473CAF58BECD5FCAF0=40AM0PR03MB?= =?utf-8?q?6051=2Eeurprd03=2Eprod=2Eoutlook=2Ecom=3E?=
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Won't this break things, e.g., in a situation where a local name
has MX in external DNS?
That is probably fairly rare and fixable by adding similar MX records
locally, but at least users should be warned about the possibility.
On the other hand does it really fix anything other than annoyance?
Non-type-specific DNS queries hardly ever happen other than manually
anyway.
Tapani
On Tue, Apr 28, 2020 at 12:23:57AM +0200, Giovanni Aneloni (giovanni.aneloni(a)live.com) wrote:
>
> Fixes: https://bugzilla.ipfire.org/show_bug.cgi?id=12391
> Change local zone to "trasnparent" instead of "typetrasnparent" to avoid
> NXDOMAIN when querying local hosts
>
> Signed-off-by: Giovanni Aneloni <giovanni.aneloni(a)live.com>
> ---
> diff --git a/src/initscripts/system/unbound b/src/initscripts/system/unbound
> index acbf6f5b5..825ac74ec 100644
> --- a/src/initscripts/system/unbound
> +++ b/src/initscripts/system/unbound
> @@ -81,7 +81,7 @@ write_hosts_conf() {
> # Skip empty domainnames
> [ "${domainname}" = "" ] && continue
>
> - echo "local-zone: ${domainname} typetransparent"
> + echo "local-zone: ${domainname} transparent"
> done < /var/ipfire/main/hosts | sort -u
>
> # Add all hosts
--
Tapani Tarvainen
next reply other threads:[~2020-04-28 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 6:13 Tapani Tarvainen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-07 21:18 Michael Tremer
2020-04-28 10:03 R: " Tapani Tarvainen
2020-04-28 10:31 ` Michael Tremer
2020-04-28 10:35 ` Tapani Tarvainen
2020-04-28 10:37 ` Michael Tremer
2020-04-28 4:55 Peter Müller
2020-04-27 22:23 Giovanni Aneloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200428061327.GA19346@tarvainen.info \
--to=ipfire@tapanitarvainen.fi \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox