On 6/17/21 9:47 PM, Tim via users wrote:
Tim:
I think if you want to modify *anything* in the zone files, you'll
first need to stop the service then delete their journal files,
before editing them.
Chris Adams:
Or just freeze/thaw them - no need to stop the server, and you should
never delete
Tim:
>> I think if you want to modify *anything* in the zone files, you'll
>> first need to stop the service then delete their journal files,
>> before editing them.
Chris Adams:
> Or just freeze/thaw them - no need to stop the server, and you should
> never delete the journal files.
I can't reme
On 6/16/21 10:45 PM, Ed Greshko wrote:
On 17/06/2021 13:41, Todd Chester via users wrote:
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows
"enabled".
Every time I have upgraded Fedora to a new release,
I have had to "enable" named-c
On 17/06/2021 13:41, Todd Chester via users wrote:
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows "enabled".
Every time I have upgraded Fedora to a new release,
I have had to "enable" named-chroot. If I ever
figure it out, I will
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows
"enabled".
Every time I have upgraded Fedora to a new release,
I have had to "enable" named-chroot. If I ever
figure it out, I will definitely get back.
:'(
Maybe it is the universe
On 16/06/2021 11:44, ToddAndMargo via users wrote:
On 6/15/21 8:03 PM, Ed Greshko wrote:
In other words, help them to help you by reproducing it and collecting as much
relevant
data.
If I ever get it figured out, I will report back
OK Just as another date point.
I rebuilt the bind-9
Once upon a time, Tim via users said:
> I think if you want to modify *anything* in the zone files, you'll
> first need to stop the service then delete their journal files, before
> editing them.
Or just freeze/thaw them - no need to stop the server, and you should
never delete the journal files.
On Wed, 2021-06-16 at 12:15 -0700, ToddAndMargo via users wrote:
> I have been know to delete them at times, but
> I don't remember why. Maybe because I wanted to
> advance the serial manually.
I think if you want to modify *anything* in the zone files, you'll
first need to stop the service then
On 6/16/21 12:10 PM, Ed Greshko wrote:
On 17/06/2021 02:59, ToddAndMargo via users wrote:
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mo
On 17/06/2021 02:59, ToddAndMargo via users wrote:
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused
with bind/named)
You can see the mounts after starting named-chroot.
Hi E
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
ch
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused
with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
chroot directory too?
Yes.
--
Remind me
On 6/15/21 2:30 PM, Ed Greshko wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
chroot directory too?
-T
A fun double check:
Doub
On 6/15/21 8:03 PM, Ed Greshko wrote:
In other words, help them to help you by reproducing it and collecting as much relevant
data.
If I ever get it figured out, I will report back
___
users mailing list -- users@lists.fedoraproject.org
To unsubscri
On 16/06/2021 11:02, ToddAndMargo via users wrote:
On 6/15/21 7:50 PM, Ed Greshko wrote:
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
Oh I screwed up a bunch. What did I post
four revisions?
My "mistake" was tyin
On 16/06/2021 11:01, ToddAndMargo via users wrote:
On 6/15/21 7:54 PM, Ed Greshko wrote:
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
On 6/15/21 7:50 PM, Ed Greshko wrote:
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
Oh I screwed up a bunch. What did I post
four revisions?
___
users mailing list -- user
On 6/15/21 7:54 PM, Ed Greshko wrote:
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following b
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, t
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
--
Remind me to ignore comments which aren't germane to the thread.
___
users mailing list -- users@lists.fedoraproject.org
To uns
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, that didn't happen all my cases of upgrades. So, I d
On 16/06/2021 09:55, ToddAndMargo via users wrote:
Hm. I screwed up pretty good. I will do this again.
I believe you've made mistakes in other areas.
I believe you've added files, with named stopped in (for example)
/var/named/chroot/etc.
This is a normal running named-chroot system.
On 6/15/21 6:57 PM, ToddAndMargo via users wrote:
On 6/14/21 10:00 PM, ToddAndMargo via 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
I hope this is the last time
On 15/06/2021 13:00, ToddAndMargo via users wrote:
Bind-chroot upgrade from FC3 to FC34 disables the service breaking a server
https://bugzilla.redhat.com/show_bug.cgi?id=1972000
Since that BZ lacks much in the area of detail why don't you:
1. Install F33 in VM.
2. Configure a named-chroot s
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, that didn't happen all my cases of upgrades. So, I doubt that was done by
the maintainers.
On 6/14/21 10:00 PM, ToddAndMargo via 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 revised, revised note. Ed had to
straighten me out on some boo-boo
On 6/15/21 2:30 PM, Ed Greshko wrote:
On 16/06/2021 03:54, ToddAndMargo via users wrote:
3) the new version of bind-chroot enables "dns security validation" by
default.
Make sure you do not have two `named.root.key` kicking around. One in
/etc/named.root.key
and one in
/va
On 16/06/2021 03:54, ToddAndMargo via users wrote:
3) the new version of bind-chroot enables "dns security validation" by default.
Make sure you do not have two `named.root.key` kicking around. One in
/etc/named.root.key
and one in
/var/named/chroot/etc/named.root.key
I th
On 6/14/21 10:00 PM, ToddAndMargo via 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 to named.root.key
Br
On 6/14/21 11:21 PM, Samuel Sieb wrote:
On 2021-06-14 10:00 p.m., ToddAndMargo via users wrote:
# systemctl enable named-chroot.service
# systemctl start named-chroot.service
In case you didn't know, "enable --now" will enable and also start the
service and "disable --now" wi
On 2021-06-14 10:00 p.m., ToddAndMargo via users wrote:
# systemctl enable named-chroot.service
# systemctl start named-chroot.service
In case you didn't know, "enable --now" will enable and also start the
service and "disable --now" will disable and stop it.
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 Int
32 matches
Mail list logo
