<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/include/name-server-ipv4-ipv6-port.xml.i, branch feature/T9082-codeql-cpp</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-05-17T04:10:36+00:00</updated>
<entry>
<title>T5226: Combine ipv4-address and ipv6-address validators</title>
<updated>2023-05-17T04:10:36+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-05-17T01:49:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=96d846d27ac818ee9a23bb7194bb58cfb7093387'/>
<id>urn:sha1:96d846d27ac818ee9a23bb7194bb58cfb7093387</id>
<content type='text'>
Use a single ip-address validator to combine and replace ipv4-address
and ipv6-address validators.
</content>
</entry>
<entry>
<title>dns: T5115: Support custom port for name servers for forwarding zones.</title>
<updated>2023-03-28T15:16:07+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-03-27T08:56:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=2bb5c5d0fd9ed07649b81a61e9c1a78a9f222405'/>
<id>urn:sha1:2bb5c5d0fd9ed07649b81a61e9c1a78a9f222405</id>
<content type='text'>
This would allow using custom ports in name server operating on non-
default port for forwarding zones.

This is a follow-up to T5113 for sake of completeness and having
consistent treatment of all name servers configured in PowerDNS recursor.

Additionally, migrate `service dns forwarding domain example.com server`
to `service dns forwarding domain foo3.com name-server` for consistency
and reusability.
</content>
</entry>
<entry>
<title>dns: T5113: Support custom port for name-server forwarders</title>
<updated>2023-03-27T06:42:38+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-03-25T23:51:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=c6494f12f92746cc4603fceca6b1a22fed010b93'/>
<id>urn:sha1:c6494f12f92746cc4603fceca6b1a22fed010b93</id>
<content type='text'>
Support custom port for name-server forwarders that would allow using
custom ports in name server forwarders to enable forwarding to
alternative name servers (unbound, stubby, dnscrypt-proxy etc.)
operating on non-default port.

This would also allow using DNS Over TLS in PowerDNS Recursor 4.6 onwards
(pdns doesn't support certificate check for validity yet) by enabling
'dot-to-port-853'. This is set by default if compiled in with DoT support.
See: https://doc.powerdns.com/recursor/settings.html#dot-to-port-853

This also partially implements T921, T2195 (DoT without certificate check).

Implementation details:
- In 'dns/forwarding' configuration, 'name-server' now allows optional
  'port' (defaults to 53).
- Instead of modifying 'name-server-ipv4-ipv6.xml.i' to add optional
  'port', a new file 'name-server-ipv4-ipv6-port.xml.i' has been used
  to avoid impacting other places where it is reused because not all of
  them honor ports (mostly VPN related).
- The `host:port` entries to be used by PowerDNS recursor config are
  normalized eagerly at the point of loading VyOS `Config` instead of
  doing them lazily while rendering the Jinja2 template to keep the
  implementation less intrusive. The alternative would entail making
  quite a bit of change in how 'vyos-hostsd' processes 'static'
  'name_servers' entries or persists their runtime states.
</content>
</entry>
</feed>
