| Description |
This article describes how to add Connection-specific DNS suffix in DHCP server setting in handing over to Internal DHCP client machines. |
| Scope | FortiGate. |
| Solution |
First, enable DHCP services in FortiGate Firewall under the interface: Go to Network -> Interfaces -> Enable DHCP server on port3 -> Select OK.
Configure a connection-specific DNS suffix in the DHCP server in FortiGate firewall via the CLI: Search for the ID where the interface port3 is configured. In this case, it is ID #3:
show system dhcp server config system dhcp server edit 1 set ntp-service local set default-gateway 10.255.1.1 set netmask 255.255.255.0 set interface "fortilink" config ip-range edit 1 set start-ip 10.255.1.2 set end-ip 10.255.1.254 next end set vci-match enable set vci-string "FortiSwitch" "FortiExtender" next edit 2 set dns-service default set default-gateway 192.168.9.1 set netmask 255.255.255.0 set interface "vlan-10" config ip-range edit 1 set start-ip 192.168.9.100 set end-ip 192.168.9.101 next end config reserved-address edit 1 set ip 192.168.9.100\ set mac ca:0a:20:7a:00:00 next end next edit 3 set dns-service default set default-gateway 172.16.10.1 set netmask 255.255.255.0 set interface "port3" config ip-range edit 1 set start-ip 172.16.10.2 set end-ip 172.16.10.254 next
To add a connection-specific DNS suffix in a DHCP server in FortiGate with the CLI, run the following:
config system dhcp server edit 3 set domain test.local end
To verify if the client is getting the connection-specific DNS suffix test.local, open a command prompt on the client machine enter the following commands:
ipconfig /release ipconfig /renew
|
