Oh, so this test raised a false positive on me. It depends on the network to be correct and not do redirection things (like the network I'm currently on does.) Therefore, it's not a terribly reliable test.

I'd entertain ignoring it, or we need to rewrite the assertion to guarantee that it can't actually resolve things (which depends on say, a DNS mock or something, and that's hard.) We can probably trust that the JVM will properly throw the right exception for us. Unless this is a runtime exception, at which point we should really make the method throw a particular exception, and not have phantom exceptions :(