Actions
Bug #4480
closed
DHCP self-reported hostnames not synced properly
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
02/27/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.5
Affected Architecture:
amd64
Description
Hello,
I noticed that if a few of my servers are set up to self-report hostnames to DHCP (active lease type), the self-reported hostnames don't get properly synced between the 2 firewalls.
For ex. one hostname only shows on one of the firewalls and another hostname shows on only the other firewalls.
Screenshot attached. I'm able to ping "db1-fast" but not "db2-fast" (probably because the db2-fast name is only present on the second firewall and the
lookups are being served by the first firewall).
Files
Updated by 
Updated by Eduard Rozenberg about 9 years ago
Thanks, I'd tried searching for existing bugs on this one but there were so many items mentioning DHCP that I couldn't locate it :).
I'll use statically assigned DHCP entries for now until a fix comes out.
Actions