It will occur when the Shorewall configuration is compiled, and
DEFER_DNS_RESOLUTION=Yes will not override that behavior.
-Tom
On 2/3/2025 6:32 AM, Christophe PEREZ via Shorewall-users wrote:
Le Sun, 2 Feb 2025 21:20:06 -0800, Tom Eastep a écrit :
The best workaround is to resolve these DNS
Le Sun, 2 Feb 2025 21:20:06 -0800, Tom Eastep a écrit :
> The best workaround is to resolve these DNS names in the params file and
> assign the result to a shell variable; then expand the shell variable
> where you need to use the address(es).
Just out of curiosity, I have a question:
The DNS res
You are correct - it is the hyphen. In these contexts, Shorewall accepts
an IP address range (-). A hyphen in a DNS name is
therefore being processed accordingly.
As Shorewall is no longer maintained, that is not going to change (and
I'm not sure I would have changed it if I were still support
On 02/02/2025 21:19, Tuomo Soini via Shorewall-users wrote:
Hyphen is not the issue. Issue is non-fqdn hostname, I'd guess.
Documentation is very clear, it advices against dns names.
Please read this part of documentation carefully and please, don't use
dns name in config.
https://shorewall.org/
On Sun, 2 Feb 2025 12:31:03 +
Philip Pemberton via Shorewall-users
wrote:
> Hi,
>
> I've been trying to add a DNAT rule which refers to a server whose
> hostname includes a hyphen:
>
> SMTP/DNAT net loc:int-mailserver
>
> Shorewall rejects this with an error in the macro
