Thanks -- it really helps a lot to know that it's not resolved in Chicago. It was registered yesterday morning or Sunday night, and all the tests I can run do return with ns1.dreamhost.com (which is why I was thinking it had propigated). And while I know dns propigation is supposed to take 1-3 days, I've never had it take even two hours (perhaps I live in a quickly-propigating area, if there is such a thing!), and here this is going on the end of the second day.
I did hear back from support already, who assure me that the domain is properly configured on their nameserver machines, contrary to the error messages. One thing I hadn't thought about was perhaps if the dns works in point A (here), maybe it won't work for hosting until it works at whatever point DH is physically at... that might explain the weird error messages.
Anyway, thanks -- if anybody else thinks there's something wrong (not DNS propigation) from the log above, please let me know.