DF-Flag on UDP-based sockets?

2022-11-29 Thread Tom
Hi list Regarding ARM 9.18.9 (https://bind9.readthedocs.io/en/v9_18_9/reference.html#namedconf-statement-edns-udp-size): "The named now sets the DON’T FRAGMENT flag on outgoing UDP packets." Tested with BIND-9.18.9, I didn't saw any UDP packets, where the "DF"-flag was set on the IP header

Re: forwarder cache

2022-11-29 Thread Hamid Maadani
> 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

2022-11-29 Thread Darren Ankney
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

2022-11-29 Thread Hamid Maadani
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

2022-11-29 Thread Darren Ankney
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

2022-11-29 Thread Hamid Maadani
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

Re: Add TXT records for SPF when CNAME exists in same sub-domain

2022-11-29 Thread G.W. Haywood via bind-users
Hi there, On Tue, 29 Nov 2022, Mark Andrews wrote: Chris Liesfield wrote: > It appears TXT and CNAME records for the same string/host cannot > co-exist. We are able to specify an SPF record for the origin only > in each sub-domain. > > Open to any suggestions on how to get around this