Foreman not picking up new TFTP Server IP Address

I have a Foreman server running in my vCenter with 2 network interfaces:

Nic1 - - Routable network
Nic2 - - L2 PortGroup

Devices connected to the new subnet can get an ip boot but showing DHCP IP - Where do i change this to

Modified the /etc/dhcp/dhcpd.conf and restarted dhcpd service

Here is the dhcpd.conf:

# dhcpd.conf
omapi-port 7911;

default-lease-time 43200;
max-lease-time 86400;
not authoritative;
ddns-update-style none;
option domain-name "ashlab.ops";
option domain-name-servers;
#option domain-name-servers;   # Tried to update this but didn't
option ntp-servers none;

allow booting;
allow bootp;
option    on;  # set the "O" and "S" flag bits
option fqdn.rcode2            255;
option pxegrub code 150 = text ;

# Bootfile Handoff
option architecture code 93 = unsigned integer 16 ;
if option architecture = 00:06 {
  filename "grub2/shim.efi";
} elsif option architecture = 00:07 {
  filename "grub2/shim.efi";
} elsif option architecture = 00:09 {
  filename "grub2/shim.efi";
} else {
  filename "pxelinux.0";

log-facility local7;

include "/etc/dhcp/dhcpd.hosts";
# ashlab.ops
subnet netmask {
  option subnet-mask;
  option routers;
  option domain-name-servers;
subnet netmask {
  option domain-name-servers;
  option subnet-mask;
  #option routers;

Another Questions: Is it possible to define the next-server ip address inside the subnet body??? so it changes depending which network is connected to?? This is because the second subnet cannot hit the foreman server using the primary IP.

Expected outcome:
Should be pointing to new DHCP Server IP

Foreman and Proxy versions:
Foreman 1.22.0
Foreman and Proxy plugin versions:

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)


Did you make sure to restart dhcpd after making the change?

Yes I did restart the service after making changes to the dhcpd.conf file but during pxe it will still pickup the same wrong DHCP IP. Rebooting did not fix the issue either.

I think the last thing i did was rung the foreman-installer with the --foreman-proxy-dhcp-server switch but it wiped my other configuration…