New Member

Solved

Run DNS server or allow DNS requests to traverse security zones?

Forum|Forum|11 years ago
November 11, 2014
5 replies
8044 views

I recently helped a customer go from a completely flat network into a segmented network. They only have one DNS server which sits on their server network. I'm finding that over half of my sessions are related to DNS queries coming from clients on other networks trying to get to the server network.

Does it make more sense for me to run a DNS server on the firewall and forward DNS queries or should I continue to let DNS traffic traverse the firewall?

I'm running a 300c on 5.0.7 and averaging around 15k sessions during peak usage. In the current setup it often peaks out the CPU but memory stays around 40%.

Best answer by ede_pfau

You could shorten DNS session life to reduce the session table size.

This will

1. reduce the number of DNS sessions at any time, thus reduce memory usage

2. increase CPU load as more build-up/tear-down action is needed

If you look at the session table of your FGT you will probably see DNS sessions with a life span up to 600 seconds, the default. I'd say that DNS sessions would not have to live longer than 1 minute or so.

You might experiment with this, in off-peak hours of course. The session lifetime is set in the CLI.

emnoc

New Member

Regardless if it's handled by the fortigate or sent to the server DNS, it's still a session by all means

As far as 15K dns session per peak hours that seems odd.

Have you track these sessions to see if;

they are valid

infect host

count the number of nxdomain

ensured nothing is inffected

etc..

FortiAdamAuthor

New Member

Sorry I should have been more specific with the session count. 15k was my overall average, not just DNS sessions. From 1p-2p today I had 175318 DNS sessions compared to 139371 HTTP sessions.

My faulty logic lead me to believe that running a DNS server on the firewall for each interface would keep me from having open DNS sessions but apparently that isn't the case?

emnoc

New Member

My faulty logic lead me to believe that running a DNS server on the firewall for each interface would keep me from having open DNS sessions but apparently that isn't the case?

Will yes, it's a local policy and policy-id0 is the match

Also the fortigate would generate 2 policies for local client using the fortigate for a lookup

Leg1: client to FGT ( name-server )

Leg2: FGT to external name-server

(for the recursive lookup )

So no matter if you route across a interface or server locally, you will always have a session.

ede_pfauAnswer

SuperUser

You could shorten DNS session life to reduce the session table size.

This will

1. reduce the number of DNS sessions at any time, thus reduce memory usage

2. increase CPU load as more build-up/tear-down action is needed

If you look at the session table of your FGT you will probably see DNS sessions with a life span up to 600 seconds, the default. I'd say that DNS sessions would not have to live longer than 1 minute or so.

You might experiment with this, in off-peak hours of course. The session lifetime is set in the CLI.

Mark_Oakton

New Member

I would suggest not having the firewall act as the dns server, either allow traffic out and dont log or use a separate dns service (FortiDNS)

Sign up

Login with SSO

Login to the community

Login with SSO