Age | Commit message (Collapse) | Author |
|
When generating a configuration for DNS domain forward to a local server
with 'set service dns forwarding domain foo.com server 1.1.1.1' this resulted in
# domain ... server ...
forward-zones=bar.com = 2.1.1.1;2.1.1.2
forward-zones=foo.com = 1.1.1.1;1.1.1.2
On PowerDNS recursor restart the last line won and it totally forgot about
'bar.com'. This could be seen from the logfiles that only one domain was loaded:
Redirecting queries for zone 'foo.com.' to: 1.1.1.1:53, 1.1.1.2:53
The manual at https://doc.powerdns.com/3/recursor/settings/#forward-zones shows
that all domains have to be configured on one 'forward-zones=' line. In the above
example this has to result in:
forward-zones=bar.com=2.1.1.1;2.1.1.2, foo.com=1.1.1.1;1.1.1.2
A subsequent check within the logfiles reveal that it's now working:
Redirecting queries for zone 'bar.com.' to: 2.2.2.2:53, 2.2.2.1:53
Redirecting queries for zone 'foo.com.' to: 1.1.1.1:53, 1.1.1.2:53
|
|
* upstream/current:
Do not try to decode data read from /sys files in the show version script, it's already an str.
Dependencies on file and pystache, for install and show version scripts..
Add dependency on hvinfo, too.
T637, T638: add dependencies on tcpdump and bmon.
T638: new op mode CLI for the bandwidth monitor commands.
T637: new op mode for traffic dumps based on tcpdump.
Correct the logic of generating tag nodes for op mode.
Add missing vyos.base module
Fix cron interval regex to allow single digit values.
Fix misplaces ConfigError exception.
Some more valueless fixes.
Mark nodes in SSH and NTP valueless (related to T602).
|
|
|
|
|
|
it's already an str.
|
|
|
|
|
|
|
|
|
|
|
|
Unlike conf mode tag nodes, op mode "pseudo-tag nodes" have the real
node.def inside the node.tag dir rather than at the top level.
The required node.def at the top level is populated with the help string
from the real one.
A side effect is that commands that take arguments now must have their own
words, e.g. "run show arp" and "run show arp eth0" is impossible and has to be
"run show arp" and "run show arp interface eth0", which is probably a good thing.
|
|
Add missing vyos.base module
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
existing interface definitions.
|
|
|
|
the type in generated command templates.
|
|
|
|
* ssh-rewrite:
T631: small bugfix in config parsind for deny-users
T631: improve help for access-control
T631: refactor SSH script and switch to jinja2
T631: first full generated config file with XML and Python
T631: use completionHelp for SSH rather then valueHelp
T631: Rewrite SSH configuration as XML interface definition
|
|
|
|
|
|
|
|
Commit f1bbc20716 ("Add jinja2 and ipaddrcheck to dependencies.")
introduced access to a NoneType object when the service was removed.
This happened after:
$ delete service dns forwarding
$ commit
File "/opt/vyatta/sbin/vyos-config-dns-forwarding.py", line 201, in <module>
verify(c)
File "/opt/vyatta/sbin/vyos-config-dns-forwarding.py", line 164, in verify
if not dns['interfaces']:
TypeError: 'NoneType' object is not subscriptable
|
|
|
|
|
|
SSH is already probed for some possible values. ALso use completionHelp
for available ciphers. In addition drop 'perl' from helper script in favor of
'tr'.
|
|
|
|
|
|
|
|
* t623-ntp-rewrite:
Switch to DNS hostnames for NTP servers
T623: Rewrite NTP subsystem in new XML style interface definition
|
|
|
|
|
|
|
|
|
|
By accident "type: txt" was removed from the wrong file...
|
|
|
|
|
|
|
|
If a user configures 'set service dns forwarding dhcp <if>' and <if> is not a
DHCP interface, this won't corrupt the recursor.conf.
The missconfiguration is simply ignored.
|
|
* powerdns-recursor:
Update debian/changelog - 1.0.4
Makefile: Fix for special nodes not requiring have any 'type' field
dns-forwarding: XML: fix indention
dns-forwarding: add completion helper for dhcp
T560: dns-forwarding: replace dnsmasq with pdns-recursor
dns-forwarding: XML: Bugfix DNS domain forward configuration nodes
dns-forwarding.py: add missing 'query-all-servers' path
Initial working version for XML interface to configure dnsmasq
Initial CLI interface support for XML DNS forwarder
|
|
|
|
... this is due to the fact that the XML generator will always add
"type: txt" to node.def files if no other type has been especially
defined.
This will break the following commands
* set service dns forwarding system
* set service dns forwarding ignore-hosts-file
because they will now have "type: txt" in their node.def file and this
will break the CLI commands. "type: txt" requires an argument but those
nodes did not in the past.
|
|
|
|
cpo@LR1# set service dns forwarding dhcp
Possible completions:
<text> Use nameservers received from DHCP server for specified interface
eth0
eth1
lo
|