Re: forwarder cache

> Have fun arguing about whether or not a server which is "authoritative" > should have an NS record in the zone, once you have something which > demonstrably works. > I don't have a lot of patience for "experts" who can't demonstrate a working > system, so I probably won't be back. Not sure

Re: forwarder cache

Errata.. On Thu, 1 Dec 2022, Fred Morris wrote: "authoritative" zone served by an authoritative server configured to return complete 1024/1025 responses look like? 1034/1035 -- FWM -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the

Re: forwarder cache

On Thu, 1 Dec 2022, Hamid Maadani wrote: [...] I can see "AUTHORITY: 0" in the answer, and now I understand NS1 does not cache this because of that (did not know only authority 1 answers are cached when I sent the initial email. Confusion of causes and effects: "AUTHORITY:0" is reportage

Re: forwarder cache

Hmm.. odd. Understood, let me go fix that. Appreciate the help. Regards Hamid Maadani December 1, 2022 9:05 AM, "Ondřej Surý" mailto:ond...@isc.org?to=%22Ond%C5%99ej%20Sur%C3%BD%22%20)> wrote: test.com (http://test.com/). 0 IN A 10.10.10.10 I think this line just have it all - you are

Re: forwarder cache

> test.com . 0 IN A 10.10.10.10 I think this line just have it all - you are generating record with TTL 0. > ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 FTR it's an authoritative answer. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org My working hours

Re: forwarder cache

> Yes, you were and still are - yet again, you don't give us full picture and > you are guessing what might be wrong.> And yet this quickly turned from "why > does cache doesn't work" into "I'm developing DLZ module and it doesn't work > as expected". > No, it's a waste of time if you don't tell

Re: forwarder cache

> On 30. 11. 2022, at 22:17, Hamid Maadani wrote: > > Ondrej, I have not been "withholding" or "censoring" information. Yes, you were and still are - yet again, you don't give us full picture and you are guessing what might be wrong. > Instead of dumping all data on you guys, I have tried to

Re: forwarder cache

> If you want the help from other people in this mailing list, withholding and > censoring information isn’t the way forward. Please stop wasting everyone’s > time by providing incomplete information. The fact that you are running DLZ on > the NS2 is important, the other important information is

Re: forwarder cache

If you want the help from other people in this mailing list, withholding and censoring information isn’t the way forward. Please stop wasting everyone’s time by providing incomplete information. The fact that you are running DLZ on the NS2 is important, the other important information is how

Re: forwarder cache

> Weird. Please send complete configs as attachments, along with a minimal > test.com zone file required to start the server and we can have a look. I think I have narrowed this down a bit. Let's see if the new info helps. I will upload the complete config otherwise. For context, I have

Re: forwarder cache

On 30. 11. 22 4:31, Hamid Maadani wrote: > That looks like, if the stale config options are removed, then NS1 > can't get an answer from NS2 at all? Or you are saying that's what > you get if NS2 isn't running and you query NS1 regarding test.com > without the stale config options? It

Re: forwarder cache

I just noticed another difference between our configurations. You have: dnssec-validation yes; and I have dnssec-validation auto; The manual says you need additional configuration if you have "yes" set: https://bind9.readthedocs.io/en/v9_18_9/dnssec-guide.html#dnssec-validation-explained

Re: forwarder cache

> That looks like, if the stale config options are removed, then NS1 > can't get an answer from NS2 at all? Or you are saying that's what > you get if NS2 isn't running and you query NS1 regarding test.com > without the stale config options? It would be the latter, I removed stale configs from

Re: forwarder cache

On Tue, Nov 29, 2022 at 5:27 PM Hamid Maadani wrote: > If I comment out the stale config options, reload and query test.com, I just > get this in logs: > 29-Nov-2022 21:57:49.931 queries: info: client @0x7f325e5a2108 > 192.168.56.1#57660 (test.com): query: test.com IN A +E(0) (172.17.0.3) >

Re: forwarder cache

Thank you for your response, Darren. Appreciate that. > I do have my forwarders setup differently (ie: I have them only on a per > domain level instead of at the options level) > Not sure how that would make a difference for the problem you are having, > however. Just to double check, I

Re: forwarder cache

I have a sort of similar configuration to this in my home network. I have two recursive servers and two "authoritative" servers (for a domain I call "mylocal" which has forward and also in.addr.arpa for my inside network). These are all running on one Intel NUC. The only difference is that my

forwarder cache

Hi there, I am running two instances of named on the same server (BIND 9.16.33 on alpine 3.16). They are running using completely separate config directories, and they have separate work directories as well as control ports. Let's call them NS1 and NS2. NS1 is a forwarding instance. It