Re: ISC DHCPv6-BIND9 DDNS update problem

On 9.6.2022. 16:50, Simon wrote:

> Mirsad Goran Todorovac <[email protected]> wrote:
>> It seems that I have identified the culprit. Our subnet has 6 rogue DHCPv6 servers according to this nmap scan:
> Yeah, that would do it. Time to get out the clue bat, or “clue by four”, and start some user education :D
Well, that would displease the Heavens above 😇 . Certainly, the Author 
of my story wants me to persevere in longsuffering of the ignorant.The 
narrow path ;-)
> But more seriously, on a network of any size, and especially if using RAs to trigger use of DHCP for address assignment, your network infrastructure should at the very least alert you to rogue DHCP servers - and preferably block them (by filtering the packets) at the edge switch ports. Without that, as you’ve experienced, anyone can start up a rogue service - whether accidentally or maliciously.
> The same applies to RAs - without rogue detection and isolation, anyone can break your network and/or hijack traffic.

Unfortunately, I am not even the admin of all those net segments and 
rogue devices. I might be simply out of luck with this one.
As Al Pacino said once, "Nobody wins 'em all!"

Kind regards,
Mirsad

-- 
Mirsad Todorovac
CARNet system engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb
Republic of Croatia, the European Union
--
CARNet sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu

-- 
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users