It's good practice in general. There might be other fields that were not explicitly set, or the struct may expand in future versions, or you have union fields/bitfields (e.g. you explicitly set the low order bits of some union field to some value, thinking the high order bits are all zeroes, but because you neglected to zero them out first, they're filled with garbage bits. when you read the union field as a whole you'll get incorrect values).
struct sockaddr_in address; ... memset(&address, 0, sizeof(address));
Can someone explain me why you need to set memory of sockaddr_in to 0 ? (Even if &address haven't been touched).