search for: dangeruser

...prefer. And now since I filed a bug and reported the crash and provided narrative and files and have seen 0 movement on the bug, I wonder why I wasted my time reporting it. If I was missing something I would hope at least a reply requesting more info or whatever would be forthcoming. Maybe Rodney Dangeruser "Don't get no respect"? ;) Well, at least "upstream". > > --keith Bill

On 2015-01-23, Warren Young <wyml at etr-usa.com> wrote: > On Jan 23, 2015, at 12:35 PM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > >> I do prefer 3ware web RAID admin >> interface anything else (it more transparently prevents me from making >> fatal blunders - probably just me). > > No, not just you. tw_cli is needlessly confusing in its

On 05/08/2019 09:55, Patrik via samba wrote: > the dig is wrong as well, it adds an additional ip address, which i have > not request to use other interfaces: > root at server:/# dig p3x-dc.patrikx3.com > Patrik, I have told you what your problem is, refusing to accept that you have setup Bind9 incorrectly is no reason for opening a new thread. Just in case you missed it, or

If i may. Rowland is right, below is not going to work as you want it to work. Bind9_flatfile with samba will be removed soon, because.. Its not supported. Read : https://wiki.samba.org/index.php/The_Samba_AD_DNS_Back_Ends Which states. Do not use the BIND9_FLATFILE DNS back end. It is not supported and will be removed in the future. And then this part. [router-logs] path =

but as i shown in my config i use bind9, why do you say i am using BIND9_FLATFILE DNS? root at server:/# cat etc/bind/named.conf.local // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; // the order is important!!!! first internal, then external!!! view "internal-enp1s0f3" { match-clients {