Although some might call it a feature! IIRC it is caused by the introduction of synchronous boot processing. Basically, fstab is being processed before networking has finished coming online so fstab just skips any mounts that require networking.
I just had a quick google and it looks like you need to set the mountnfs.sh script to run asynchronously. See the details here.
It's a known 'issue' in Debian
Although some might call it a feature! IIRC it is caused by the introduction of synchronous boot processing. Basically, fstab is being processed before networking has finished coming online so fstab just skips any mounts that require networking.
I just had a quick google and it looks like you need to set the mountnfs.sh script to run asynchronously. See the details here.