> On 27 Aug 2024, at 06:04, Havard Eidnes via bind-users
> wrote:
>
>> On Mon, Aug 26, 2024 at 06:05:19PM +0200, Havard Eidnes via bind-users wrote:
>>> Thanks. I found it, and it's more than a little embarassing.
>>>
>>> This is what you get when not building with --with-libxml2: an
>>> "un
> On Mon, Aug 26, 2024 at 06:05:19PM +0200, Havard Eidnes via bind-users wrote:
>> Thanks. I found it, and it's more than a little embarassing.
>>
>> This is what you get when not building with --with-libxml2: an
>> "un-rendered" xsl file as a result, in essence just the content
>> of bin/named/x
On Mon, Aug 26, 2024 at 06:05:19PM +0200, Havard Eidnes via bind-users wrote:
> Thanks. I found it, and it's more than a little embarassing.
>
> This is what you get when not building with --with-libxml2: an
> "un-rendered" xsl file as a result, in essence just the content
> of bin/named/xsl.c.
> If I was debugging this I would:
> - compared strace output from working and non-working server
I did parts of that, ref. that other message I sent.
> Unfortunately you are the only person who reported this problem and I
> can't reproduce it either, so it's probably up to you to find needle
> i
Hi Petr,
great that you mention where to look into the code, I'm not familiar
with it yet. This is certainly what I'm looking for, the search
algorithm for a client IP to find its view. The lab test depends on an
investment in a Supernic (and the appropriate chassis/Motherboard/PCI
architectu
BTW,
I got an off-line question how the chrooting is done in my case,
i.e. whether the "chroot" program is used, or the "-t" option to
BIND is used.
In my case it's the latter:
-t directory
This option tells named to chroot to directory after processing
the com
On 26. 08. 24 9:19, Havard Eidnes via bind-users wrote:
Looking a bit further, I find in the XML output:
Server Status
Boot time:
So no actual value? Is there a required post-processing step
whi
On 25. 08. 24 9:20, Greg Choules via bind-users wrote:
Regarding view selection, I don't know exactly how the code works or how
efficient it is. But certainly I have seen some configs with a lot of
views and they seem to function OK.
Views are matched one by one, you can have a look at functio
Hi,
and thanks for the suggestions.
This is not an issue of broken clocks, all the involved machines
run ntp and have good sync status traceable to at least a GPS clock.
This does however appear to have something to do with the
chroot'edness of this particular installation, and it's evident that
>> Hi Håvard.
>> Have you tried a different browser?
>
> Not yet. Will do tomorrow.
Latest Chrome on MacOS: just the same; it displays the raw XML
which isn't exactly user-friendly.
Regards,
- Håvard
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC
Looking a bit further, I find in the XML output:
Server Status
Boot time:
So no actual value? Is there a required post-processing step
which is omitted? I see xsl is mentioned both here and in the
style
Hi there,
On Mon, 26 Aug 2024, Greg Choules wrote:
On Sun, 25 Aug 2024 at 21:06, Havard Eidnes via bind-users <
I've started testing 9.20.x.
... firefox ... version 120.0... informs me ...
This XML file does not appear to have any style information
associated with it. The document tree i
Latest Chrome/Safari/Firefox on MacOS as well and it looks good for me. I
haven't needed to clear cookies or browsing data or anything, it just
worked.
My 9.20.0 is running locally on the Mac, installed via homebrew. Maybe try
that and see what you get?
Perhaps it's something to do with the enviro
On further reflection I suspect broken clocks. Named uses If-Modified-Since to
determine
whether to resend the style file. Named uses the server’s start time as the
modification time
in that calculation.
> On 26 Aug 2024, at 11:06, Mark Andrews wrote:
>
> We are probably not properly managin
14 matches
Mail list logo
