In Domain Driven Design, one of the defining characteristic of an Entity is that it has an identity.
Problem:
I am not able to provide a uni
I cannot begin to use Guid values at this point.
Yes you can and that would be an alternative. Guids would not be your database primary keys but rather would be used at the domain model level. In this approach you could even have two separate models - a persistence model with ints as primary keys and guids as attributes and another model, the domain model, where guids play the role of identifiers.
This way your domain objects can get their identities once created and persistence is just one of minor business concerns.
The other option known to me is the one you described.