Displaying 20 results from an estimated 3000 matches similar to: "Another way to transfer zones"
2005 Dec 05
1
ANNOUNCEMENT: NSD 2.3.2 released
NSD 2.3.2 is a bugfix release.
Please see the README document for configuration and installation
instructions.
You can download NSD from http://www.nlnetlabs.nl/nsd/
Note: we switched to SHA-1 for tarball digest.
2.3.2
=============
FEATURES:
- Bug #101: add support for the SPF record.
BUG FIXES:
- Bug #100: replaced non-portable use of timegm(3) with
portable
2009 Apr 05
1
Segfault in Sieve 1.2
Hello,
two days ago I've upgraded to 1.2rc2 and the new sieve implementation
(version 0.1.4). Today I got the first mail that got stuck in the
postfix queue because deliver was dying with a segfault.
The mail is spam, thus I don't have any issues sharing it:
http://users.birkenwald.de/~berni/temp/deliver-segfault.mail
It happens with this small sieve script (my normal one is larger, but
2007 Jul 10
1
nsdc update implementation details
Hi,
I have a query regarding running a manual update of nsd via:
# nsdc update
My NSD server is accepting notifications from two servers. From my
nsd.conf:
# master 1
allow-notify: X.X.X.X NOKEY
request-xfr: AXFR X.X.X.X NOKEY
# master 2
allow-notify: Y.Y.Y.Y NOKEY
request-xfr: AXFR Y.Y.Y.Y NOKEY
Are both servers sequentially queried each time
2006 Dec 16
0
NSD 3: adding zones without restarting?
I try to change the configuration of a runnung NSD 3 instance. "nsdc
reload" apparently does not read the config (only the database). "nsdc
restart" seems to do the trick but is there a way to have the
configuration change taken into account without stopping the service
for the time it takes to restart?
2012 Mar 05
3
IXFR regression in nsd 3.2.9?
We upgraded to NSD 3.2.9 (from 3.2.8) because we encountered the
problem "Fix denial of existence response for empty non-terminal that
looks like a NSEC3-only domain (but has data below it)." (a nasty
problem with DNSSEC). But we now have IXFR issues.
On one name server, NSD 3.2.9 works fine, zones are IXFRed and work.
On another name server, with much more zones (and big ones), we
2015 Jan 29
2
quota_full_tempfail = yes broken with lmtp_rcpt_check_quota (was: Re: lmtp_rcpt_check_quota not working)
Bernhard Schmidt <berni at birkenwald.de> wrote:
Hi,
> Axel Luttgens <AxelLuttgens at swing.be> wrote:
>
> Hi Axel,
>
>> Le 11 f?vr. 2014 ? 08:34, Bernhard Schmidt a ?crit :
>>
>>> [...]
>>> so Dovecot should reject in RCPT TO phase, but according to the logs of the
>>> upstream Postfix it does so after END-OF-DATA
>>>
2006 Dec 07
1
a few more notes
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".
2005 Oct 12
1
build-nsdzones.pl and nsd.zones fileformat
hi,
I noticed the build-nsdzones.pl only converts the first zone of my
named.conf to nsd.zones. It also did not include either a master or
notify keyword, even though my bind configuration for that zone had an
also-notify keyword. Even not listing an also-notify line did not cause
build-nsdzones.pl to process more then one zone.
Second, I had a question about the nsd.zones format. Does the
2024 Jan 12
1
error: cannot write zone : Permission denied
Hello,
NSD 4.8.0 running on FreeBSD 13.2-RELEASE-p9 and serving both plain
and DNSSEC signed zones.
I noticed Permission denied errors in the logs for all domains listed
in nsd.conf:
[2024-01-12 12:20:05.710] nsd[8655]: info: writing zone
domain-plain.org to file domain-plain.org
[2024-01-12 12:20:05.710] nsd[8655]: error: cannot write zone
domain-plain.org file domain-plain.org~: Permission
2013 Oct 18
1
nsd-4.0.0b5(and rc2) and changing zone from master to slave ?
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
2012 Jul 23
1
[PATCH] nsd-patch: fix segfault after renaming slave zone
Hi all,
we have discovered a segfault in nsd-patch when renaming slave zone in nsd
config file if some data for this zone still exists in the IXFR diff
database.
In my case, the zone "black" was renamed to "blackinwhite":
> root at ggd115:/cage/nsd/var/nsd/zones#nsd-patch -c
> /cage/nsd/etc/nsd-dns-slave.conf
> reading database
> reading updates to database
>
2003 Jul 21
0
nsd replies with NOTIMP when receiving a NOTIFY?
The primary (a BIND9) of a zone ("test.") served (as a secondary) by
our nsd complains:
Jul 16 17:52:45.796 notify: debug 3: zone test/IN: notify response from 192.134.7.251#53: NOTIMP
After all, nsd implements the NOTIFY, it logs them and SEC parses the
log file to run "nsdc update". Isn't it an error to send a NOTIMP?
nsd 1.2.1
2004 Aug 07
1
multiple instances of NSD
I'm trying to set up a machine which will be running multiple instances
of NSD to serve different sets of zones from different interfaces. What
I'm running into is that I can't specify different PID files to refer to
on the command line.
Are there any shortcuts or do I need to go write a patch?
Any other implications of multiple instances?
--
2006 Dec 10
5
which is the vaild a format?
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:
2012 Jun 08
2
Best practices to switch from BIND to NSD
Hi,
I'm a sys admin and currently working for a french hosting company. We
provide DNS services to our customers and at the moment we are using BIND
on Debian servers. BIND is a good software but we don't need a recursing
DNS for our public DNS, and we needed better security than what BIND provides.
So I made the suggestion to replace BIND by another DNS software.
NSD appears to be the
2023 Jul 21
1
Adding SRV records to zone
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
>
>
2011 Oct 30
1
reloading NSD zone configuration
Good morning,
On Tue Apr 28 2009 at 10:34:24 CEST, Jelte Jansen wrote:
> We are looking into it (if only because the question comes up about once a
> week now)
It's been a little more than a week since the question last turned up :)
I'd also like to know if any progress has been made to allow NSD to have
zones added/removed on the fly, somewhat along the lines of BIND's
2023 Jul 21
1
Adding SRV records to zone
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,
2023 Mar 20
2
NSD zone file GENERATE directive
On 3/20/23 13:41, Anand Buddhdev via nsd-users wrote:
> Hi Robert,
>
> NSD doesn't understand the GENERATE directive. You'll have to create
> your zone files using a script or template engine.
Understood but certainly not helpful with large dynamic IPv6 PTR's...
Not that dynamic hosts NEED PTR's, but would still be nice to have.
--
inoc.net!rblayzor
XMPP:
2023 Mar 20
1
NSD zone file GENERATE directive
Robert Blayzor via nsd-users writes:
> > NSD doesn't understand the GENERATE directive. You'll have to create
> > your zone files using a script or template engine.
> Understood but certainly not helpful with large dynamic IPv6 PTR's...
> Not that dynamic hosts NEED PTR's, but would still be nice to have.
lex(1) is your friend. For managing our reverse ip6