Showing results for 
Search instead for 
Did you mean: 


DNS Servers per DHCP Pool on FTD/FDM

I'm glad not to be the only person complaining about this. DHCP flexibility on a NGFW FTD device is all but completely useless compared to the older ASA. I don't mean to be so unkind toward Cisco, but the FTD requires a significant amount of priming and digging. I've lost weeks of time trying to work around these limitations, and finding myself in sheer regret, and costing Cisco at least a dozen unresolved TAC cases.


For DHCP limitations:

  • You cannot provide DHCP on a sub-interface
  • You cannot provide DHCP options
  • You cannot provide separate DNS servers per DHCP pool.

What Cisco has done is wreck the small/branch office offerings with a baffling exclusion of these options, not to mention many other very important functions that are badly needed to be carried over from ASA.


That said, you can hack it, but you have to apply specific options via the Lina_cli tool, and they're not perpetual. You must manually re-apply them each time you push changes to the device:


In expert mode:

sudo su

LinaConfigTool "dhcpd dns [dns_server_2] [dns_server_2] interface [interface]"

Example: LinaConfigTool "dhcpd dns interface inside"
Again, while this solves the problem of providing different DNS servers per pool, you must re-apply them each time you deploy any changes to the device through FDM and probably FMC.

The reason is, the deployment code overwrites everything that doesn't match the committed changes, unfortunately. You can't be selective like you can with other tools.

"You can't fix what you can't see"

RFC 1925

Thanks for the information,


But how about running multiple commands at a time , like enabling an specific interface


Interface Gi1/1

no shutdown


How we can run this using LinaConfigTool .





I believe you can do it this way:


LinaConfigTool "interface Ethernet1/7" "ip address" "no shut"


where the subsequent commands are simply separated by a space. That said, not every instance of this works. For example, "nameif", and "security-level", which seem to have been deprecated, and it could be that this example will also fail. There's no way to predict it, and obviously there's no readily handy documentation or "useful" Command Reference.


I learned this example from an FDM failure, where it could not "un-do" something it deployed successfully.

RFC 1925

I wanted to comment an update. 7.0.0 code for the FTD, and we still have a blacklisted/blocked dhcpd dns command. Why? This makes for quite a challenge for smaller sites where the FTD needs to supply DHCP, but we don't wish to use the same DNS per VLAN/interface.

dhcpd dns interface byod

dhcpd dns interface inside


RFC 1925
Piotr Kowalczyk

I know, this is old post, but perhaps somebody found a solution for this issue? I mean LinaConfigTool "dhcpd dns interface [interface]" works well and would do for me, but it doesn't stay after restart and I didn't found the way to save it to srtup-config.

Recognize Your Peers
Content for Community-Ad