The ping works perfectly :
==================
PING la_guerre_d_espagne.crealinks.net (209.15.98.76): 56 data bytes
64 bytes from 209.15.98.76: icmp_seq=0 ttl=235 time=205.355 ms
[...]
64 bytes from 209.15.98.76: icmp_seq=9 ttl=235 time=168.575 ms
--- la_guerre_d_espagne.crealinks.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 164.164/171.758/205.355 ms
==================
Beside that, you are confusing the transportation information on the net driven by RFCs and what a server does. And a server is NOT driven by RFC, it just has to comply with interface on the net.
For instance, if you want to have an email like
john%smith%senior.mydomain.com and not
[email protected] you are perfectly authorized by RFC to do so. (see RFC 819). Of course, this is not an easy way, because you have to rewrite the sofware on the server at mydomain.com , but it is perfectly "legal".
About the naming convention for subdomains, the RFC says that the convention for naming third level and over (ie subdomains and sub subdomains) are given by the higher level. In other terms, it is the responsability of domain owner to give the rules for subdomains.
(i'm not sepaking about IDNA, but only use of USASCII)
Michel Lo