From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.6.0
Date: Fri, 16 Dec 2016 16:44:07 +0100 [thread overview]
Message-ID: <7c43c6e5-d892-977a-d72b-c3bae6da15dc@ipfire.org> (raw)
In-Reply-To: <1481889567.13949.289.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2790 bytes --]
Hi,
unbound 1.6.0 - with reverted commit - is running here since a few hours
without seen problems so far - we'll see.
One question, being curious:
Could it make sense to compile 'unbound' using '--with-pthreads' for
threading support?
I got the following in '_build.ipfire.log' right now:
...
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for pthread_spinlock_t... yes
checking for pthread_rwlock_t... yes
checking if -pthread unused during linking... no
...
In this regard, I read
https://www.unbound.net/documentation/howto_optimise.html, but I'm not
so skilled in programming to judge whether this would lead to any
advantages...
Best,
Matthias
On 16.12.2016 12:59, Michael Tremer wrote:
> Hi,
>
> that server is not available from the internet. But that you get that IP address
> is enough for me. That didn't happen before.
>
> I will revert that commit and we will see in the testing if this raises any
> problems again...
>
> Best,
> -Michael
>
> On Fri, 2016-12-16 at 12:47 +0100, Matthias Fischer wrote:
>> Hi,
>>
>> On 16.12.2016 11:28, Michael Tremer wrote:
>> >
>> > Did you try reverting this one and test if things like
>> > "pakfirehub01.i.ipfire.org" resolve again?
>>
>> I just tested after adding "qname-minimisation: yes" and
>> "harden-below-nxdomain: yes" to '/etc/unbound/unbound.conf', but neither
>> "pakfirehub01.i.ipfire.org" nor its ip-address "172.28.1.165" answered.
>>
>> No connection through browser, ping loss on both = 100%.
>>
>> With or without, I get the following answer with 'dig':
>>
>> ...
>> root(a)ipfire: /etc/unbound # dig pakfirehub01.i.ipfire.org
>>
>> ; <<>> DiG 9.10.3-P4 <<>> pakfirehub01.i.ipfire.org
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45016
>> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 4096
>> ;; QUESTION SECTION:
>> ;pakfirehub01.i.ipfire.org. IN A
>>
>> ;; ANSWER SECTION:
>> pakfirehub01.i.ipfire.org. 293 IN A 172.28.1.165
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 127.0.0.1#53(127.0.0.1)
>> ;; WHEN: Fri Dec 16 12:33:28 CET 2016
>> ;; MSG SIZE rcvd: 70
>> ...
>>
>> Best,
>> Matthias
>>
>
next prev parent reply other threads:[~2016-12-16 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 8:50 Matthias Fischer
2016-12-16 10:28 ` Michael Tremer
2016-12-16 11:47 ` Matthias Fischer
2016-12-16 11:59 ` Michael Tremer
2016-12-16 15:44 ` Matthias Fischer [this message]
2016-12-16 16:13 ` Michael Tremer
2016-12-16 16:39 ` Matthias Fischer
2016-12-16 16:42 ` Michael Tremer
2016-12-16 17:52 ` Matthias Fischer
2016-12-18 18:07 ` Michael Tremer
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=7c43c6e5-d892-977a-d72b-c3bae6da15dc@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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