| 4:04 am on Jul 15, 2009 (gmt 0)|
|Wonder if Azure would be open to providing validation schemes for their clients? |
You mean like MS has been doing at 131.107. since 2003 ;)
| 4:05 am on Jul 15, 2009 (gmt 0)|
Great. More 'bots with dynamic, un-ascribable IP addresses.
On the other hand, I already have 'serious trust issues' with Microsoft, ranging from the malformed MSN user-agent strings, to the "tide" hosts issuing their bogus search referrals, to the various past malfunctions in msnbot's handling of robots.txt and on-page robots metatags, to the lack of rDNS on many requests from their IP blocks... IMO, Bing works amazingly well considering the extreme 'sloppiness' of their infrastructure compared to other search providers.
If Azure's IP blocks are not well-partitioned away from other MS services, I will likely just pull the plug and block the lot of them; Google, Yahoo, and Ask traffic will just have to do -- as before.
| 6:22 am on Jul 15, 2009 (gmt 0)|
My trust issues with Microsoft have led me to block anything that looks like it's coming from them on all but one of my sites; I need to know what they're up to.
This will likely be one more thing to block. Just like I do with AWS. Unless they manage to implement some form of validation scheme--perhaps like the one Lord Majestic claims to be working on. But I think we all know how likely that is.
Bill, will we be permitted to post the Azure IP ranges as they become known to us so anyone who wants to can add them to their ban lists?
| 11:23 am on Jul 15, 2009 (gmt 0)|
NetRange: 220.127.116.11 - 18.104.22.168
CIDR: 22.214.171.124/17, 126.96.36.199/18
| 7:10 pm on Jul 15, 2009 (gmt 0)|
Thanks for the IP range. Blocked. MS is bad enough at the best of times.
I see the /18 above that is unallocated: watch out for expansion?
| 9:35 pm on Jul 15, 2009 (gmt 0)|
|Bill, will we be permitted to post the Azure IP ranges as they become known to us so anyone who wants to can add them to their ban lists? |
I think thetrasher beat everyone to it! :)
Not sure that's the range they'll be using but it'll be easy to spot stuff bouncing off my firewall when it starts to happen.
| 12:59 am on Jul 16, 2009 (gmt 0)|
|but it'll be easy to spot stuff bouncing off my firewall when it starts to happen. |
I really should write a script to track stuff like that and incorporate it into my weekly report. I have no idea what UAs are getting blocked at the door based on IP Address bans.