Re: shorewall dynip problem
- To: email@example.com
- Subject: Re: shorewall dynip problem
- From: "Philippe Gaudron" <firstname.lastname@example.org>
- Date: Thu, 23 Jan 2003 20:05:32 +0100
- Message-id: <3E304B0C.3334.55A2F76@localhost>
- In-reply-to: <1043336541.784.57.camel@helium>
> Helo all !
> ACCEPT:info net:thelaptop.dynip.com loc:192.168.0.10 tcp
> http,https - all
As said in shorewall documentation
- WARNING: I personally recommend strongly against using DNS names in Shorewall
- When a DNS name appears in a rule, the iptables utility resolves the name to
one or more IP addresses and inserts those addresses into the rule. So changes
in the DNS->IP address relationship that occur after the firewall has started
have absolutely no effect on the firewall's ruleset.
You have to find another way to restrict access to your internal Web server :(
Authentication, SSL ?