You can do this now: wget http://216.46.192.85/
Using DNS is just a convenience after all, not a requirement. Mark Post -----Original Message----- From: Dan Jacobson [mailto:[EMAIL PROTECTED] Sent: Saturday, November 15, 2003 4:00 PM To: [EMAIL PROTECTED] Subject: feature request: --second-guess-the-dns I see there is --bind-address=ADDRESS When making client TCP/IP connections, "bind()" to ADDRESS on the local machine. ADDRESS may be specified as a hostname or IP address. This option can be useful if your machine is bound to multiple IPs. But I want a --second-guess-the-dns=ADDRESS so I can $ wget http://jidanni.org/ Resolving jidanni.org... done. Connecting to jidanni.org[216.46.203.182]:80... connected. HTTP request sent, awaiting response... 503 Service Unavailable $ wget --second-guess-the-dns=216.46.192.85 http://jidanni.org/ Connecting to jidanni.org[216.46.192.85]:80... connected... Even allow different port numbers there, even though we can add them after the url already: $ wget --second-guess-the-dns=216.46.192.85:66 http://jidanni.org:888/ or whatever. Also pick a better name than --second-guess-the-dns -- which is just a first guess for a name. Perhaps the user should do all this in the name server or something, but lets say he isn't root, and doesn't want to use netcat etc. either.
