Problem with hostnames starting with hyphens, stars, etc. (but works fine on windows!)

So, I'm having trouble fetching pages from a set of URLs, but only
under linux (Red Hat FC4, FC5, and ES3) not under Windows XP Pro (it
works even under cygwin in Windows). Admittedly, the URLs are poorly
chosen, and the content is garbage. But it's for a customer, and I
have no control over that.

In any case, I've tried fetching the URLs using firefox and wget from a
windows machine, and that works fine. Under linux, I've used lynx,
wget and telnet to port 80 (not gonna set up X11 just to debug this
issue!). Always I get an error:

lynx: Unable to connect to remote host.
telnet/wget: Name or service not known

but, host (mind your "--" to stop argument processing) reveals:

-zero.piczo.com has address 64.124.63.70

And I can telnet, wget, lynx, etc. fine to that numeric address.

Finally, a list of example URLs that I'm working with:

http://*rommi*.piczo.com/?cr=4&rfm=y
http://-------sweetly-------.piczo.com/?cr=6&rfm=y

I'm totally stumped on this one...

Best,
Dav

Hello,

Dav Clark a écrit :
[...]
> In any case, I've tried fetching the URLs using firefox and wget from a
> windows machine, and that works fine. Under linux, I've used lynx,
> wget and telnet to port 80 (not gonna set up X11 just to debug this
> issue!). Always I get an error:
>
> lynx: Unable to connect to remote host.
> telnet/wget: Name or service not known
[...]
> Finally, a list of example URLs that I'm working with:
>
> http://*rommi*.piczo.com/?cr=4&rfm=y
> http://-------sweetly-------.piczo.com/?cr=6&rfm=y

These hostnames are just invalid.
From RFC 1912 - Common DNS Operational and Configuration Errors :

DNS domain names consist of "labels" separated by single dots. The
DNS is very liberal in its rules for the allowable characters in a
domain name. However, if a domain name is used to name a host, it
should follow rules restricting host names. Further if a name is
used for mail, it must follow the naming rules for names in mail
addresses.

Allowable characters in a label for a host name are only ASCII
letters, digits, and the `-' character. Labels may not be all
numbers, but may have a leading digit (e.g., 3com.com). Labels must
end and begin only with a letter or digit.

I recognize that fact. This, however, does not change the fact that
someone outside of my control wishes for me to deal with these invalid
URLs. And, currently, I can't do this on anthing but a windows
machine.

Surely I should be able to co-erce linux into using these URLs (which
do actually resolve with host)?

DC

Pascal Hambourg wrote:

> These hostnames are just invalid.
> From RFC 1912 - Common DNS Operational and Configuration Errors :
>
> DNS domain names consist of "labels" separated by single dots. The
> DNS is very liberal in its rules for the allowable characters in a
> domain name. However, if a domain name is used to name a host, it
> should follow rules restricting host names. Further if a name is
> used for mail, it must follow the naming rules for names in mail
> addresses.
>
> Allowable characters in a label for a host name are only ASCII
> letters, digits, and the `-' character. Labels may not be all
> numbers, but may have a leading digit (e.g., 3com.com). Labels must
> end and begin only with a letter or digit.

On Tue, 2006-10-31 at 10:21 -0800, Dav Clark wrote:

> Surely I should be able to co-erce linux into using these URLs (which
> do actually resolve with host)?

You are right, sure you could "co-erce" GNU/Linux to use it, ... you
have all sources available, so shoot:

- bind
- mozilla
- glibc

When you finish "co-ercing" those get back here, I give you more so you
can use http://*g'o`'o**!*#le.c0m !



> DC
>
> Pascal Hambourg wrote:
>
> > These hostnames are just invalid.
> > From RFC 1912 - Common DNS Operational and Configuration Errors :
> >
> > DNS domain names consist of "labels" separated by single dots. The
> > DNS is very liberal in its rules for the allowable characters in a
> > domain name. However, if a domain name is used to name a host, it
> > should follow rules restricting host names. Further if a name is
> > used for mail, it must follow the naming rules for names in mail
> > addresses.
> >
> > Allowable characters in a label for a host name are only ASCII
> > letters, digits, and the `-' character. Labels may not be all
> > numbers, but may have a leading digit (e.g., 3com.com). Labels must
> > end and begin only with a letter or digit.
>

Johny be Good wrote:
> On Tue, 2006-10-31 at 10:21 -0800, Dav Clark wrote:
>
> > Surely I should be able to co-erce linux into using these URLs (which
> > do actually resolve with host)?
>
> You are right, sure you could "co-erce" GNU/Linux to use it, ... you
> have all sources available, so shoot:
>
> - bind
> - mozilla
> - glibc
>
> When you finish "co-ercing" those get back here, I give you more so you
> can use http://*g'o`'o**!*#le.c0m !



That's lot of work!


--
Raqueeb Hassan
Bangladesh

"Dav Clark" <(E-Mail Removed)> writes:
> Pascal Hambourg wrote:
>
> > These hostnames are just invalid.

> I recognize that fact. This, however, does not change the fact that
> someone outside of my control wishes for me to deal with these invalid
> URLs. And, currently, I can't do this on anthing but a windows
> machine.
>
> Surely I should be able to co-erce linux into using these URLs (which
> do actually resolve with host)?

Resolve with host, use the IP addresses?
--
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer