This works nicely. Note the single-parameter init of create_unicode_buffer nul-terminates:

>>> r=ctypes.create_unicode_buffer('String\0Other')
>>> r.value              # value display stops at first nul.
u'String'
>>> ''.join(r)           # gives answer similar to create_string_buffer's raw method.
u'String\x00Other\x00'

The language specification is where null is defined, and it says

There is also a special null type, the type of the expression null, which has no name. Because the null type has no name, it is impossible to declare a variable of the null type or to cast to the null type. The null reference is the only possible value of an expression of null type. The null reference can always be cast to any reference type. In practice, the programmer can ignore the null type and just pretend that null is merely a special literal that can be of any reference type. --Link to documentation (Section 4.1)

and

The null type has one value, the null reference, represented by the literal null, which is formed from ASCII characters. A null literal is always of the null type. --Link to documentation (Section 2.3)

Rather a circular sounding definition, but the value of null is the null reference itself - just another pointer. The value of the null reference isn't really relevant and is presumably up to the implementor, but zero or some other value that can't be confused with another object address is likely.

Confusion may be caused here because there is a character value called the null character with value \u0000. This is the default value for type char.