It's not a matter of propagation at all for the whois record. Unless you are reaching it from someplace where it is cached, it will always be "up to date".
Again, all you have done by changing, or adding, nameservers to your whois record is tell the system where to look for DNS records. A nameserver contains DNS records in order to facilitate the lookup.
Maybe if I repeat this a third time, in slightly different words, you will understand:
If your nameservers are set correctly in your whois record, and you are still unable to resolve the domain name to an IP address, then your DNS information on the nameservers you are using is not correct or is not current.
The registry does not hold or provide lookup information. That is done by the nameserver that is indicated in the registry. You need to discuss this with the people who run the nameserver you have indicated is to be used.
The only info that is in the whois is what nameservers to use. It should now be obvious the the information that is in (or is not in?) the DNS records maintained in those nameservers is not being successfully used to lookup the IP address of your site. This is not DreamHost's problem at all; it is a problem with your DNS reocrds in your chosen/specified nameservers.
You should do nothing more "in DreamHost", and nothing you can do at DreamHost will resolve this problem if you have correctly specified the nameservers. You can add as many nameservers as you want in your whois record at DreamHost and it will make no difference if your DNS records are not properly added to the nameservers you specify. Nothing you can do at DreamHost, and nothing DreamHost can do for you can correct a problem with your DNS records on another nameserver..........
If your current host is computinghost.com (which is whose nameserver you have said to use) you need to discuss this with them; Dreamhost can't help you with it, because
... ARE NOT DREAMHOST'S NAMESERVERS!