#SDN #Routing #Switching #Firewall #NAC #Proxy #Mail Gateway #SDWAN

Multiple Name Servers: As described in the previous tutorial on DNS , two to seven name servers can be registered against a domain name. These are DNS servers that contain information on where to find services (such as www or email) for a particular domain name. There are two main reasons for providing more than one DNS server for each domain. The first is to provide protection against a DNS server going down- if a DNS server failed for any reason (eg. power outage, communication failure etc.) the domains using this DNS server would be unobtainable since the IP address of these domains could not be retrieved. Instead, having two or more (which should be geographically and topologically seperate) means that if a request to one of them fails, the name server can be requested again. The name servers are requested and in normal circumstances, information from any of the DNS servers is used (which normally contain the same information). The chances of two DNS servers going

An information disclosure vulnerability has been discovered in OpenSSL versions 1.0.1 through 1.0.1f. This vulnerability may allow an attacker to access sensitive information from memory by sending specially-crafted TLS heartbeat requests. Impact Under certain circumstances, exploitation of this vulnerability can result in the disclosure of sensitive information. ========================================================================= Solutions A firmware update for FortiOS is available at http://support.fortinet.com . This vulnerability is fixed in FortiOS version 5.0.7. Firmware updates for FortiAuthenticator, FortiMail and FortiRecorder will be available on Friday April 11th. Firmware release dates for other products are pending. The following workarounds are available: 1. Apply the mitigating IPS signature to interface policies on affected FortiGate devices. The IPS signature was released in IPS update 4.476 and is named "OpenSSL.TLS.Heartbea

Dispatch Method Method used to determine to which server traffic is directed: Cyclic — Directs traffic to each operational server one by one (round robin). Weighted Cyclic — This method uses the Weighted Round Robin algorithm. AppDirector distributes clients’ requests for service in the round robin manner taking into consideration the weight of servers in that farm. Explicitly, every new session is distributed to the next server up to the server weight. For example, if one server has a weight of 2 and another server has wei

appdirector client view-filters create 2 -saf x.x.x.x -sat x.x.x.x appdirector client filtered-table