similar to: Adding PTR records

I'm asking that what is the proper method to add SRV records. I read the documentation but I couldn't find anything around it. If you can perhaps add something which specifies how each and every type of record is to be written on documentation, that would be very useful. Thanking you Sagar Acharya https://humaaraartha.in 21 Jul 2023, 18:46 by jeroen at nlnetlabs.nl: > Hi Sagar,

Hi Sagar, Are you getting a particular error? Because the same method should work just fine in NSD. Simply open the corresponding zone file (as configured in nsd.conf) and put that line in there. Best regards, Jeroen Koekkoek On Fri, 2023-07-21 at 09:14 +0200, Sagar Acharya via nsd-users wrote: > How do I add SRV record to my zone file? > > Eg. In pdns I have > >

How do I add SRV record to my zone file? Eg. In pdns I have _xmpp-client._tcp.example.com.? ?3600? ? ?IN? ? ?SRV? ? ? 0 5 5222 example.com Thanking you Sagar Acharya https://humaaraartha.in P.S. Please cc me, I'm not subscribed to this list.?

Per RFC 8501 seciont 2.2 https://datatracker.ietf.org/doc/html/rfc8501 I have attempted to use a wildcard on a /64 boundary within a zonefile for NSD, but it doesn't not appear to work. PTR lookups fail... tested with, ie: $ORIGIN 1.1.0.0.8.5.1.b.2.2.5.2.ip6.arpa. * PTR my.fqdn.net. Did not work... or would you have to use? (not tested) *.*.*.*.*.*.*.*.*.*.*.* PTR .... --

Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters:

Hi Chris, I'm having trouble trying to reproduce the issue locally. Like you I configure two zones. zone: name: example.com. zonefile: example.com.zone.signed zone: name: bar.example.com. zonefile: bar.example.com.zone The file bar.example.com.zone does not exist. After touching and reloading the signed zone, no segfault occurs. I've tried with and without the

Hi Jeroen, Attached is the zone I used. Did you add the record for a.bar ? Ex: a.bar 300 IN NS ns.somewhere.net. Chris ________________________________ From: Jeroen Koekkoek <jeroen at nlnetlabs.nl> Sent: Tuesday, October 8, 2024 5:33 AM To: Chris LaVallee <clavallee at edg.io>; nsd-users at lists.nlnetlabs.nl <nsd-users at lists.nlnetlabs.nl> Subject: Re:

Hi, I found a reproducible seg fault with a DNSSEC signed zone and overlapping config. I'm running NSD 4.10.1. Here's how to reproduce. 2 zones in nsd.conf: zone: name: "foo.com." zonefile: "/zones/foo.com.zone.signed" zone: name: "bar.foo.com." zonefile: "/zones/bar.foo.com.zone" Zone files:

Hi Chris, I can reproduce with your zone. Thanks! Best, Jeroen On Tue, 2024-10-08 at 14:07 +0000, Chris LaVallee wrote: > > Hi Jeroen, > > > Attached is the zone I used. Did you add the record for a.bar ? > > > Ex: > > > a.bar ? 300 ? ? IN ?NS ? ? ?ns.somewhere.net. > > > Chris > > > > > > > > > > >

Hi Chris, I've properly started looking into this yesterday. NSD definitely shouldn't crash, still working on that. However, the provided zone is invalid too(?) I'm not the foremost expert on NSEC3 (or even DNSSEC), but is seems an NSEC3 is missing for bar.foo.com. Empty non-terminals should still have an NSEC3 RR. (Of course, the delegation point should be at bar.foo.com. too and

On 03/12/15 20:54, Jonathan S. Fisher wrote: > >unless you explicitly set your site name when you provision > I guess we didn't. Is that an issue? I still wonder why that says > "null" when, even if we used the default, our sitename is not null. > No it isn't an issue, why are you now worrying about something that has nothing to do with your problem. > >

hi, while all files is owned by nsd user and nsd run as nsd the nsd.db is still owned by root user (because the compiler run as root and create this file as root, ok i know just it'd be better if this file is owned by nsd too). another strange thing is that on the slave nsd i've got such messages: ----------------------------------------- zonec: reading zone "lfarkas.org".

Hi all, We've recently migrated from a separate DNS server that was dynamically updated with BIND's update-policy, using a manually generated tkey-gssapi-keytab (plus a second server functioning as an ordinary slave to the first), to BIND9_DLZ. The setup predated Samba's AD DC support and BIND's DLZ support, and was originally established because even though we needed AD, we were

On 03/12/15 21:12, Jonathan S. Fisher wrote: > Rowland, I hear and understand you loud and clear. If you could point > out below what is the problem, because the client seems to be > configured correctly as you have asked: > > > root at freeradius:~# nslookup 192.168.127.131 > Server:192.168.127.131 > Address:192.168.127.131#53 > > Non-authoritative answer: >

Hi, I'm doing some quick tests with nsd-4.0.0b5 and (rc2). And found something strange when changing (nsd-control reconfig) one zone from: zone: name: 10.in-addr.arpa zonefile: /zones/empty.zone to zone: name: 10.in-addr.arpa request-xfr: 192.168.122.12 NOKEY allow-notify: 192.168.122.12 NOKEY zonefile: /zones/slave/10.rev and doing nsd-control reconfig. After

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

i'm posting this to the bind-users and rsync mailing lists in order to get this archived for the next person who needs to do this :) comments and suggestions are welcome, but please cc: to me because i'm not subscribed to either list. craig ----- Forwarded message from Craig Sanders <cas@taz.net.au> ----- Date: Fri, 27 Jul 2001 10:30:20 +1000 From: Craig Sanders

hi, after i test nsd i find the following. if i use this in a zone file: $ORIGIN example.com. CNAME www www CNAME x x A 1.2.3.4 then it's excepted by nsd what's more give the proper result. if the slave is nsd than there is no problem, while if the slave is bind i've got the following error:

On 04/12/2023 13:47, Jean-Christophe Boggio via nsd-users wrote: Hi Jean-Christophe, > When syncing between master and slaves, am I supposed to see new files > appear in the slave's "zonesdir" directory? Because, as you might > expect, I see nothing here. Is this behavior normal? From what I > understand, the slave "caches" the data in /var/lib/nsd/nsd.db

On Sat, 28 Dec 2019 17:02:09 +0100 richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > The problem is (was) that I used "include:" statements in nsd.conf > to load zone information. Apparently nsd does not reread the include > files upon a SIGHUP. I scripted everything into 1 file and a HUP > rereads the zone info now. Wrong, I made a mistake it