Have updated the logic further such that 

a platform developer can force dnsrand_next to help achieve the current/previous simple counter logic, if needed.

However if random dns query id is desired, then if urandom reading fails (previously it would have fallen back to the simple counter) but in turn if real time clock is available then clock_gettime is used to help reseed through srandom. However if neither (ie urandom and clock) is available, then now it still continues with the random prng, bcas anyway it is better than the simple counter at some level.

--