On Sat, 11 Jan 2014, Benny Pedersen wrote:
>> Where is my mistake?
>
> missing options rotate in resolv.conf ?
>
> unsure if its just that
>
> why is your 127.0.0.1 not providing dns service ?
>
> dont use global forwards on dns, this is stupid :)
May be you are right :-)
Any hints is welcomed.
The server is a web server.
In my opinion is better if apache and other services do name resolutions
locally instead than query externally :-)
The 127.0.0.1 works fine as cache DNS if I don't block the udp traffic.
Thanks for your hints, but returning in topic, I still don't understand
why the DNS resolutions doesn't works.
Why the rule:
DNS(ACCEPT) dmz:192.168.110.0/24 all
don't work as expected?
What am I missing?
Thanks, P.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
