We are probably not properly managing the style sheet versioning correctly.
Flushing
the browser’s cache when you install a new version of BIND should fix the
display problems.
As for collectd there are differences in which stats are collected. You a
probably
looking for something that is no
> Hi Håvard.
> Have you tried a different browser?
Not yet. Will do tomorrow.
> Having said that, I just started 9.20.0 with this config:
>
> statistics-channels { inet 127.0.1.0 port 8080 ; };
>
> Then pointed three different browsers at that address/port and it looks
> fine to me in all of the
Hi Håvard.
Have you tried a different browser? Having said that, I just started 9.20.0
with this config:
statistics-channels { inet 127.0.1.0 port 8080 ; };
Then pointed three different browsers at that address/port and it looks
fine to me in all of them.
Browers tried were Chrome, Safari and Fir
Hi,
I'm mostly running BIND 9.18.x, and have configured statistics
publishing via
statistics-channels {
inet 127.0.0.1 port 8053 allow { 127.0.0.1; };
inet "actual-address" port 8053 allow { prefix1/24; prefix2/24; };
};
I've started testing 9.20.x.
I see BIND 9.20.x stats publi
Hi Grant.
That doesn't work for zones that then get used in a `response-policy`
block. In this case you *must* define a zone §each time; so one (or up to
64) per view/instance of `response-policy`. Test it on your laptop/in a VM.
What this does mean is that (if you are using views) you *could* have
5 matches
Mail list logo
