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
>