Sync DNS with DHCP Leases
The DNS shall resolve the hosts which was provided an addressed by DHCP.
After spending a couple hours trying to figure out why i couldn't connect to any of the fqdn's I created reservations for in the v18 XG135. I found out it doesn't link DHCP to DNS. Hard to believe in any gateway devices that handles both DHCP and DNS that they aren't bound.
Jason Spangler commented
This was a feature in UTM9, why isn't it already a part of XG? Please add.
Greg Masem commented
I, too, would love to see this as an option
Steve Savenelli commented
Rather than my previous general message, I would like to see the following in the next MR (as it is standard on many other firewalls
1 - DNS Sync with DHCP
2 - DHCP client list - action buttons for revoke lease, add static entry and block from using this IP
3 - host name resolution, not FQDN
Basically tight integration between DNS and DHCP with the ability for action
Martin Holst commented
DHCP should definitely register hostnames in DNS.
Hostnames should also be visible in "Live Connections", instead of just IP-adresses.
I would like it to as for home firewall XG would be really helpfull, as it has already the list in the DHCP lease, could have option to bind ip to hostname ...
Add me to the list of people that are shocked this is not a feature, as nearly every other comparable product to the XG has this, including the old UTM9.
IT Support commented
This was in the UTM software of my SG that I'm phasing out, why is this not on here already? This is basic and should be done already. **** it should create a host that you can add to firewall rules to boot like in the UTM software.
Jess Jones commented
This is 2019, not 1999. Open source firewall software does this out of the box, why does Sophos think this doesn't merit inclusion?
AD is unnecessary garbage in a primarily Linux environment; the appliance already handles both DHCP and DNS, why on earth can't the latter do a lookup from the former's tables?
I figured it'd been a while since I'd touched Sophos products and felt it was fair to give 'em another go, but the absence of rudimentary SB/SOHO functionality like this inclines me to kick them to the curb again...
J mIchael commented
Another one here saying WHY ISNT this a feature already!??
Agreed, definitely needed.
Reading through XG docs, it seems XG almost assumes you're integrating with Active Directory, thus getting Windows DNS. Personally, I've been moving most of my smaller clients away from on-prem AD because IDaaS combined with Azure AD or Google is cost-effective and worthwhile. But this leaves me in a lurch because I still need another server to synchronize DNS with DHCP. In my case, I use a competitor's free firewall that handles DHCP and DNS nicely. These additional servers should be unnecessary.
This is needed.
Unbelieveable! Back to IPCOP then until this is "fixed" or I manage to get VPNs working on opnsense.
This seems very rudimentary if the device is handling both DNS and DHCP
I need this for a number of small office installs. Crazy it's not default, worked fine in SG...
This is to basic to be missing... Just spent hours troubleshooting a problem thats not even a feature..
Desperately needed as we deploy more clients. It is in the previous firewall, most every thing I need seems to be a "feature request"
Spent a while troubleshooting a backup issue only to figure out this was the problem. I didn't believe it wasn't native, was too used UTM9... or any other firewall I've ever used...