[dhcwg] Re: Why draft-ietf-dhc-addr-notification-13 and not DNS update instead?

On Nov 18, 2024, at 3:40 PM, Petr Menšík <[email protected]> wrote:
> But the thing is, do you need credential for DNS when you do not need any for DHCP?

  One word: history.

> Where does that security came from?

  It doesn't.

> The thing is, how is DHCP authenticated better than DNS?

  It's not.

  i.e. the DHCP client can't update DNS.  But it can put something into a DHCP packet.

  Then, the DHCP server can update DNS.  And that update can be authenticated.

> If dnsmasq would accept any DNS update over TCP for a name not already registered, how would it be different? What makes DHCP more suitable, when it is not even needed for getting an address?

  DHCP updates work precisely where DNS doesn't, because the DHCP packets from the client are unauthenticated.

  Alan DeKok.

_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]