Displaying 20 results from an estimated 900 matches similar to: "support for ALIAS records"
2024 Jan 11
1
support for ALIAS records
While SVCB/HTTPS provides a better solution for the browsing use case, I see other use cases where ALIAS/ANAME would be ideal, notably in apex RRs.
So while fostering SVCB/HTTPS deployment is a good thing, I wouldn?t mind name server software implementing ALIAS. Including NSD, but I reckon it?s much more challenging to do due to NSD architecture than it was to implement it in PowerDNS.
But if
2024 Jan 11
1
support for ALIAS records
Hi Christof!
AFAIK, PowerDNS is the only open source name server that supports ALIAS. There was an idea to standardize ALIAS as "ANAME" (https://datatracker.ietf.org/doc/draft-ietf-dnsop-aname/), but the idea was dropped in favor of SVCB/HTTPS record https://datatracker.ietf.org/doc/rfc9460/. So now we have to wait until all Browser vendors implement SVCB/HTTPS.
Regards
Klaus
PS: If
2014 Mar 24
7
[Bug 2217] New: allow using _ssh._tcp SRV records
https://bugzilla.mindrot.org/show_bug.cgi?id=2217
Bug ID: 2217
Summary: allow using _ssh._tcp SRV records
Product: Portable OpenSSH
Version: 6.5p1
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
2024 Mar 01
1
RFC8501 IPv6 Wildcard PTR
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 ....
--
2024 Feb 27
2
About timestamps in logs and zonestatus
Dear All,
Please help me understand why timestamps in logs are different from those
in nsd-control zonestatus output:
served-serial: "2024022603 since 2024-02-27T08:07:51"
commit-serial: "2024022603 since 2024-02-27T08:07:51"
Feb 26 18:47:34 slave-server nsd[780]: zone testzone.test. received update
to serial 2024022603 at 2024-02-26T18:47:33 from
2012 Jul 18
4
Unsecured zone transfers and open resolvers
Hello,
My question is not related to NSD in particular, but I have seen here on
the list a lot of people that work for TLDs and other Registrars and
Registry operators I thought it would be a good place to ask this
question. It is about DNS though, not completely off topic :).
I have encountered in my DNS studies a few name servers that let you
transfer zones they are authoritative for. The
2013 Nov 29
2
nsd 4.0 EAGAIN loop in sendmmsg(2)
On NetBSD 6.99.28-CURRENT, nsd 3.2.16 works fine, however nsd 4.0.0 is
spinning chewing CPU. The logs show:
Nov 28 23:07:00 xxx nsd[466]: sendmmsg failed: Resource temporarily
unavailable
ktruss shows it getting EAGAIN from sendmmsg(2) over and over again.
According to the man page:
[EAGAIN|EWOULDBLOCK]
The socket is marked non-blocking and the requested
2012 Nov 28
1
Build error of NSD4 on Debian Squeeze
Hello World,
I am trying to build NSD4 on Debian Squeeze and I get the following
errors when running `make`.
```
$ pwd
/home/wiz/src/nsd/tags/NSD_4_0_0_imp_5
$ make
[... output omitted ...]
gcc -g -O2 -o nsd-checkconf answer.o axfr.o buffer.o configlexer.o
configparse
acket.o query.o rbtree.o radtree.o rdata.o region-allocator.o tsig.o
tsig-opens
4_pton.o b64_ntop.o -lcrypto
configparser.o: In
2024 May 17
1
query: bad tsig signature for key
hi,
At least with a recent version if it is a time sync issue nsd will do a specific log msg that.
Laura,
can you send over the actual configuration?
(maybe replacing the key with a placeholder or rotating the keys afterwards)
It sounds strange if nsd checks tsig on the notify, but allow xfr without it.
Regards,
Tam?s
May 16, 2024 16:14:59 Anand Buddhdev via nsd-users <nsd-users at
2023 Apr 24
1
nsd issue
Hi Jean Claude,
The message is printed when the bind operation failed. Why that happens
is hard to say, I'd need more information for that. As the message does
not say: address already in use (or similar), I'm guessing the address
is not configured?
Best regards,
Jeroen
On Fri, 2023-04-21 at 18:03 +0200, HAKIZIMANA Jean Claude via nsd-users
wrote:
> Dear nsd Users,
> kindly can
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
2013 Mar 11
1
nsd4 process weirdness?
Hi,
I was playing with the munin plugin in nsd4 beta4, and saw some strange
errors. Directly after starting nsd on linux, I'm seeing:
$ ps ax -o pid,ppid,user,args | grep nsd
1638 1 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1641 1638 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1647 1641 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
$ sudo munin-run nsd_munin_memory
2024 Apr 25
3
NSD 4.10.0rc1 pre-release
NSD 4.10.0rc1 is available:
https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz
sha256 ad476e82eee5bdabc985e071cabe6a68263dd02eac6278ce2f81798b8c08f19f
pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz.asc
Version 4.10.0 integrates simdzone and drops the Flex+Bison zone
parser.
NSD used a Flex+Bison based zone parser since version 1.4.0. The parser
served NSD well, but zones have
2007 Aug 06
2
NSD reload
Hi there!
I remember reading that you cannot reload new zone files on the fly and require a full restart of the nsd daemon? We are evaluating multiple DNS servers that have better performance comparing to bind, but will require quite heavy zone reload (new and existing) every 10 minutes or so. Downtime (even 1-3 secs) is not the option. Thanks!
2019 Dec 28
2
tinydns to nsd
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
2024 Feb 28
1
About timestamps in logs and zonestatus
Hi Jeroen,
I just realised that the version I use is very old -- 4.1. So first what I
should do -- updating it and only then come here , asking for clarification.
??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>:
> Hi Peter,
>
> NSD processes updates in batches. xfrd receives the [AI]XFR and
> schedules a reload for the main process, which in turn forks
2012 Jul 18
1
allow-notify SUBNET and request-xfr inconsistency
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
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
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
>
2013 Feb 04
1
NSD 3.2.15 released (+RRL)
Dear NSD users,
Here is the release candidate for NSD 3.2.15. This comes with ILNP
support, NSD-RRL and different TSIG initialization (it fails if it can't
find no suitable algorithms, instead of can't find 'one of the'). Plus
some bugfixes.
The NSD-RRL implementation is based on the work by Vixie and Schryver.
However, because of the code-diversity argument that is at the basis