Redirecting DNS Requests to Umbrella with FTD
A few days ago I shared an article that described redirecting DNS requests with ASA. A good use case for this might be if an organization is using Cisco Umbrella but there is no way to get every host is pointed toward the correct DNS server(s) in a timely manner. In that case, a configuration of destination NAT in the ASA can force those misconfigured clients to use one of the OpenDNS addresses.
This article is very similar, but we will share a method for doing this with Firepower Threat Defence. The concept is the same but all configuration is done in Firepower Management Console. Before starting on the NAT configuration, it is important to configure the following network objects (Objects, Object Management, Network).
- obj_any – 0.0.0.0/0
- Umbrella1 – 208.67.220.220
- Umbrella2 – 208.67.222.222
It is also important to confirm the existence of two port objects (Objects, Object Management, Network).
- DNS_over_TCP – TCP Port 53
- DNS_over_UDP – UDP Port 53
Most of the configuration will be done on the NAT policy for the device we are managing (Device, NAT, select edit for the appropriate NAT policy).
We will need four rules that Continue reading

Wireless carriers say not being able to use Huawei equipment would “gravely impair” their ability to do business. And they can’t afford to “rip and replace” their equipment.
A recent survey from DigitalOcean found that half of developers said they did not have a strong understanding of serverless. Of those, a vast majority said they plan to research the topic within the next 12 months.

A new survey from SDxCentral found 71 percent or respondents use public clouds — up from just 43 percent three years ago.
Apple snubs Intel's 5G modem for its next-gen iPhone; ZTE names a new CEO; Ericsson opens a 5G lab in Delhi, India; InterDigital shows a 5G control plane.



The expansion is in the form of a new 115,000-square foot building that can support up to 21 megawatts of capacity.