Jump to content

Bug in peer resolve


schnurlos

Recommended Posts

Please fix following issue (since ever, actually on the 3.4.2 stable build 32549).

IP's like "mail.xxx.com", "mail.xxx.net" are correctly resolved, while IP's like "xxx.com", "xxx.net" are just shown with the US flag (correctly the 00 flag in flags.conf).

IP's like "xxx.at" as well as "mail.xxx.at" are always correctly shown with the AT flag, so TLD are flagged correctly.

BTW, its time to include the possibility to flag the .org, info, ... not everything is at home in the US!

Perhaps include a "world" flag/symbol for this global entries.

Link to comment
Share on other sites

Please fix following issue (since ever, actually on the 3.4.2 stable build 32549).

IP's like "mail.xxx.com", "mail.xxx.net" are correctly resolved, while IP's like "xxx.com", "xxx.net" are just shown with the US flag (correctly the 00 flag in flags.conf).

IP's like "xxx.at" as well as "mail.xxx.at" are always correctly shown with the AT flag, so TLD are flagged correctly.

BTW, its time to include the possibility to flag the .org, info, ... not everything is at home in the US!

Perhaps include a "world" flag/symbol for this global entries.

@schnurlos what about those ip address who don't have dns name like .com or something.Only ip address exists.We cannot get flag of whose ip address which don't have any dns names.Even though they will add flag for .org .info then still it would be incomplete unless they redesigned this feature from scratch.Who cares???.They are tons of feature  already have got destroyed which was working fine before.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...