On 7/1/21 9:10 AM, Petr Menšík wrote:
Hi,
On 6/30/21 5:11 AM, ToddAndMargo via bind-users wrote:
On 6/27/21 4:01 PM, Reindl Harald wrote:
seriosly i am beginning to wonder if you should simply give up bind-chroot
Never quit! :-)
Is is not a bad idea. If you are running SELinux
On 6/24/21 9:00 PM, ToddAndMargo via bind-users wrote:
Hi All,
Fedora 34
bind-chroot-9.16.16-1.fc34.x86_64
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating these two
files over into
/var/named/chroot/var
On 6/27/21 4:01 PM, Reindl Harald wrote:
seriosly i am beginning to wonder if you should simply give up bind-chroot
Never quit! :-)
it's not the job of the chroot bind-mount setup to mount each and every
file and 'file "abc.hosts.rev"' without any path makes no sense
just write your
On 6/27/21 3:40 PM, ToddAndMargo via bind-users wrote:
On 6/26/21 7:31 PM, ToddAndMargo via bind-users wrote:
On 6/24/21 9:00 PM, ToddAndMargo via bind-users wrote:
The goal is to have bind-chroot do its thing
mount --bind
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
On 6/26/21 7:31 PM, ToddAndMargo via bind-users wrote:
On 6/24/21 9:00 PM, ToddAndMargo via bind-users wrote:
The goal is to have bind-chroot do its thing
mount --bind
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
It is not occurring on my zone files. Is it suppose to?
I have
On 6/24/21 9:00 PM, ToddAndMargo via bind-users wrote:
The goal is to have bind-chroot do its thing
mount --bind
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
It is not occurring on my zone files. Is it suppose to?
___
Please visit https
Hi All,
Fedora 34
bind-chroot-9.16.16-1.fc34.x86_64
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating these two
files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with
On 6/17/21 3:12 AM, Reindl Harald wrote:
however, in the real world just write "sudo command" is the best you can
do - for the average user it's complete and leaves no questions
for power users which don't like sudo it should be no deal-breaker to
type the command without "sudo" in a root
On 6/16/21 12:45 PM, Richard T.A. Neal wrote:
On 16 June 2021 7:31 pm, ToddAndMargo wrote:
Does this alteration at the top make it any clearer?
Note: at the command prompt, I use the following terminology:
# means run as root
$ means run as user
Inside a file, "#"
Hi All,
In my named.conf
logging {
channel update_debug {
# file
"/var/named/chroot/var/named/slaves/named-update-debug.log";
file "slaves/named-update-debug.log";
severity debug 3;
print-category yes;
print-severity yes;
On 6/16/21 2:16 AM, Reindl Harald wrote:
Am 16.06.21 um 09:31 schrieb ToddAndMargo via bind-users:
...
# means root
$ means user
...
Sometimes, in your configuration file extracts, you use '#' meaning
'this line is a comment'. I guess this is a write-up for a novice.
The non-novices here
On 6/15/21 11:54 PM, G.W. Haywood via bind-users wrote:
Hi there,
On Wed, 16 Jun 2021, ToddAndMargo wrote:
Re: My FC33->FC34 bind-chroot upgrade notes
I hope this is the last time I have to revise this!
...
Unfortunately perhaps not.
:'(
...
# means root
$ means user
...
Sometimes,
On 6/15/21 6:59 PM, ToddAndMargo via bind-users wrote:
On 6/15/21 12:51 PM, ToddAndMargo via bind-users wrote:
On 6/14/21 10:02 PM, ToddAndMargo via bind-users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes
On 6/15/21 12:51 PM, ToddAndMargo via bind-users wrote:
On 6/14/21 10:02 PM, ToddAndMargo via bind-users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Here are my
On 6/14/21 10:02 PM, ToddAndMargo via bind-users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Well, if at first you don't succeed, revise! See
changes
On 15-06-2021 07:46, ToddAndMargo via bind-users wrote:
On 6/14/21 9:30 PM, Jim Popovitch via bind-users wrote:
On Tue, 2021-06-15 at 14:27 +1000, Mark Andrews wrote:
https://downloads.isc.org/isc/bind9/9.16.16/doc/arm/Bv9ARM.pdf
The modern-day RTFM :-)
-Jim P.
"Just G
On 6/14/21 9:30 PM, Jim Popovitch via bind-users wrote:
On Tue, 2021-06-15 at 14:27 +1000, Mark Andrews wrote:
https://downloads.isc.org/isc/bind9/9.16.16/doc/arm/Bv9ARM.pdf
The modern-day RTFM :-)
-Jim P.
"Just Google it." The new RTFM. Chuckle!
And ' 'managed-keys' is deprecated" is
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Broken bind-chroot repair after upgrading to Fedora 34:
# means root
$ means user
1) temporary workaround so you can surf the
Hi All,
Fedora 34
bind 9.16
The Duck is failing me.
Placing
include "/etc/named.root.key";
in my bind.conf, give me the following error:
# named-checkconf -l -t /var/named/chroot /etc/named.conf
/etc/named.root.key:1: option 'managed-keys' is deprecated
What do I use in its place?
Many
On 6/13/21 12:13 AM, ToddAndMargo via bind-users wrote:
On 6/12/21 11:47 PM, ToddAndMargo via bind-users wrote:
Oh but no errors and it still does not work!
# host 8.8.8.8
Host 8.8.8.8.in-addr.arpa not found: 2(SERVFAIL)
# host 8.8.8.8 8.8.4.4
Using domain server:
Name: 8.8.4.4
Address
On 6/12/21 11:47 PM, ToddAndMargo via bind-users wrote:
Oh but no errors and it still does not work!
# host 8.8.8.8
Host 8.8.8.8.in-addr.arpa not found: 2(SERVFAIL)
# host 8.8.8.8 8.8.4.4
Using domain server:
Name: 8.8.4.4
Address: 8.8.4.4#53
Aliases: 8.8.8.8.in-addr.arpa domain name pointer
Oh but no errors and it still does not work!
# host 8.8.8.8
Host 8.8.8.8.in-addr.arpa not found: 2(SERVFAIL)
# host 8.8.8.8 8.8.4.4
Using domain server:
Name: 8.8.4.4
Address: 8.8.4.4#53
Aliases: 8.8.8.8.in-addr.arpa domain name pointer dns.google.
and nothing appeared in /var/log/messages
On 6/12/21 5:30 PM, ToddAndMargo via bind-users wrote:
Hi All,
I just upgraded from Fedora 33 to Fedora 34.
Bind was updated from 9.11 to 9.16 in Fedora 34.
It completely broke my Fedora 33 configuration.
Would someone please point me to the directions
as to how to migrate from 9.11 to 9.16
On 6/12/21 10:55 PM, Ondřej Surý wrote:
Most likely SELinux policy is preventing access to those files. Check the other
logs.
Ondřej
--
Ondřej Surý — ISC (He/Him)
No SE Linux error popping up. But I shut it off temporarily anyway. No
symptom change. Rats!
# setenforce Permissive
#
On 6/12/21 8:30 PM, ToddAndMargo via bind-users wrote:
# named-checkzone -t /var/named/chroot/var/named/slaves abc.local
abc.hosts.rev
abc.hosts.rev:3: ignoring out-of-zone data (255.168.192.in-addr.arpa)
abc.hosts.rev:14: ignoring out-of-zone data
abc.hosts(10.255.168.192.in-addr.arpa
On 6/12/21 7:49 PM, Mark Andrews wrote:
Please don’t hid details if you want help.
If you really want help post all the un-doctored log messages.
B.T.W. The messages below are because you used the wrong zone name on the
named-checkconf command line. The zone file is for xyz.local and you
On 6/12/21 5:30 PM, ToddAndMargo via bind-users wrote:
Hi All,
I just upgraded from Fedora 33 to Fedora 34.
Bind was updated from 9.11 to 9.16 in Fedora 34.
It completely broke my Fedora 33 configuration.
Would someone please point me to the directions
as to how to migrate from 9.11 to 9.16
Hi All,
I just upgraded from Fedora 33 to Fedora 34.
Bind was updated from 9.11 to 9.16 in Fedora 34.
It completely broke my Fedora 33 configuration.
Would someone please point me to the directions
as to how to migrate from 9.11 to 9.16?
Many thanks,
-T
28 matches
Mail list logo
