No DNS-resolution after going to "unbound"

[Robert Huff]

On 3/25/2014 11:49 AM, Ewald Jenisch wrote:

>> 25-Mar-2014 00:23:53.218 no longer listening on ::#53
>> 25-Mar-2014 00:23:53.218 no longer listening on 209.6.39.223#53
>> 25-Mar-2014 00:23:53.218 no longer listening on 10.0.0.1#53
>> 25-Mar-2014 00:23:53.218 no longer listening on 127.0.0.1#53
>
> This explain why there's no DNS resolution. What we still don't know
> is why unbound stops listening (or doesn't even start to listen in the
> first place).

	Using bind99, not unbound.  (See previous post.)

> I assume, there's no firewall or such thing on your machine too, right?

	Oh, yes, there's a firewall ... which handled this absolutely correctly 
two days ago.


				Robert Huff