When you run nsupdate to add a record, you must specify a Time-To-Live value (TTL) for it to specify the maximum time the record can be cached by any resolver DNS server before querying an authoritative DNS server for an up-to-date version of the record again. This is true for all record types. The TTL value goes in between the name and the record type.

If you wanted to specify a TTL of 7200 seconds (2 hours), for example:

$ sudo nsupdate > update add _kerberos.EXAMPLE.COM 7200 URI 10 1 krb5srv:m:tcp:kdc1.example.com 

If your nearest DNS server is the authoritative one for your DNS zone, and the record is used locally only, then the TTL value might not be very important, but it still needs to be specified.

When you run nsupdate to add a record, you must specify a Time-To-Live value (TTL) for it to specify the maximum time the record can be cached by any resolver DNS server before querying an authoritative DNS server for an up-to-date version of the record again. This is true for all record types. The TTL value goes in between the name and the record type.

If you wanted to specify a TTL of 7200 seconds (2 hours), for example:

$ sudo nsupdate > update add _kerberos.EXAMPLE.COM 7200 URI 10 1 "krb5srv:m:tcp:kdc1.example.com" 

Please also note the double quotes around the string.

If your nearest DNS server is the authoritative one for your DNS zone, and the record is used locally only, then the TTL value might not be very important, but it still needs to be specified.