v0.26.1: EDNS(0) support, better error message, AXFR fixes
Major bug fixes since v0.26.0:
A node can now start with no configured peer if its registry is enabled
This allows to run a name registry without having to input a dummy peer
into the configuration file.
Default interface
settings have been changed
The default interface setting, used when no interfaces
section is present
in the config file, has been changed from one HTTP endpoint on port 2826
and one RPC endpoint on port 2571 to one RPC endpoint on port 2826
(the default RPC endpoint from now on) and one HTTP endpoint on 8080.
DNS: Fixed AXFR regression from v0.26.0
v0.26.0 inadvertently introduced a regression which made the node
always reject AXFR requests even for zones they know about.
DNS: AXFR requires to use a subdomain
The AXFR query for zone a.b
needed to be performed on foo.a.b
(where foo
is any valid string). This has been fixed and the node
will now answer AXFR properly.
Improved network-sent error messages
In the recent releases, Agora has made more use of reusable exception.
This correlated with a decrease in the quality of error messages,
as the HTTP framework didn't understand them.
This has been changed, and error message will now be properly sent,
instead of the unhelpful "And Exception has occured".
EDNS(0) support was added
The DNS server will now include an OPT record if one was sent in the query,
as well as honor the requested payload size, and set the TC flag when needed.
Do not add empty addresses to the list of banned/whitelisted nodes
This would happen when the RPC interface was in use, leading to nodes failing
to load their banlist / whitelist on restart.