forum.utorrent.com

Here's a few I found
200.120.110.20
pc-20-110-120-200.cm.vtr.net (Chile)
vtr.net|CL

209.105.205.79
nbdsl2-79.onlink.net (Canada)
onlink.net|CA

67.141.100.178
h178.100.141.67.ip.alltel.net
alltel.net|US

Also, could you merge Firon's list with your one? Thanks

You don't need to map US hosts.
The US flag shows by default for com/net.

Last edited by Firon (2005-11-09 20:18:32)

As Firon said, .com, .org, .net, and other generic TLD's are already mapped to the US flag, so the only relevant two in your list would be these two:

nextgentel.com|NO
as15444.net|UK

few more :]

ms012.net|YU
sksyu.net|YU

Last edited by vBm (2005-11-10 06:58:55)

alshamil.net.ae for UAE
etisalat.ae for UAE

Last edited by inajmi (2005-11-10 05:25:22)

vBm wrote:

few more :]

Updated. I saved the file in *nix so the line breaks are different. I'm not sure if this matters or not, but after I get off work I can save it with Windows style line breaks if it's a problem.

tjobo wrote:

You guys know that you can always use the:
Resolve countries using ip->country online database. (In advanced, options)

That option doesn't seem to work when using a .conf file. All the .com/.net will have no flags when that option is on, at least that's what it did when I turned it on last night.

inajmi wrote:

alshamil.net.ae for UAE
etisalat.ae for UAE

Hostnames ending with .ae should already have the UAE flag, at least with my .conf file. I'm pretty sure the default one doesn't have the .ae TLD mapped to a flag.

Last edited by eng (2005-11-10 09:31:26)

chaosblade wrote:

Here's the one me & firon collected over time

Added those yesterday ;-)

How strange, it seems like US flags really do disappear when using custom TLDs...
I tried with unix and dos line feeds, no difference. Removing all US mappings didn't make a difference either. Maybe it's a bug...

Removing all mappings doesn't matter, peer.resolve_country simply doesn't work with a flags.conf present. I guess it's to prevent conflicts between the two?

Last edited by Firon (2005-11-10 19:18:11)

Found these hostnames:

amis.net|SI
auna.net|ES
awalnet.net|SA
bezeqint.net|IL
bornet.net|SE
bredband2.com|SE
bt.net|UK
csloxinfo.net|TH
cwjamaica.com|JM
cybersurf.com|CA
e7even.com|UK
eircom.net|IE
eth.net|IN
gibconnect.com|GI
kingston.net|CA
lijbrandt.net|NL
cwpanama.net|PA
link.net|EG
mediaWays.net|DE
nextgentel.com|NO
perspektivbredband.net|SE
plus.com|UK
proxad.net|FR
quickclic.net|CA
rima-tde.net|ES
romtelecom.net|RO
serwer.net|PL
siol.net|SI
skekraft.net|SE
t-dialin.net|DE
vif.net|CA
vtr.net|CL

Edit: If you want to check hostnames, you can do so through my webserver.
To check against a hostname, go to http://animorc.com/ipwhois/
Enter any IP-address or hostname and it should display the country code and name.
Note that it isn't perfect, but it's said to resolve 97% of all IPs/hostnames.

Will remove this if it's abused or unused

Last edited by Animorc (2005-11-12 06:54:11)

tbaytel.net|CA
enter-net.com|CA
enta.net|GB
npgco.com|US
nefkom.net|DE
tularosa.net|US

Updated.

Also noticed that the hostname mapping is case-sensitive :-(

I had taken intercable.net|MX from Firon's list way back when, but when I saw a peer from that hostname it was *.INTERCABLE.net and no flag showed up. Chaning the .conf to contain INTERCABLE.net|MX caused the correct flag to show up. If there's going to be different capitalizations of the same hostname it will be tedious to find them all.

chaosblade wrote:

half of those were already mentioned.. try reading the thread next time :p

You're right about me not reading the thread . Sorry about that.
But I wouldn't say that half of them were mentioned, and some of those which were, were wrong (siol.net|SL for instance. Don't know if SL is Slovakia, but it should be Slovenia iirc). And since eng replied that they were already updated and no flags appeared, I found it useful to enter them again.