13 May
2019
13 May
'19
4:25 p.m.
On Mon, May 13, 2019 at 11:58:18AM -0700, Roger wrote:
I wanted to thank everyone for their help with the
google issue I’m having. It is not resolved but I’ve made some discoveries. It looks like
a fair number of the ampr.org sites that come up on google may in fact be done via BGP.
Rob’s is and the others that I did a traceroute on, terminate on an address that is not
44.
But that said, I now think this is a 100% Google issue. I don’t know what kind of
stupidity they are up to but Yandex and Bing, have no problems indexing my site. I have
read of others having similar issues. Bing and Yandex actually use Google’s same system
for verification and they crawl just fine.
73
Roger
VA7LBB
After Roger mentioned that AMPRNet BGP-advertised web sites were
getting indexed, but not very many others, and then someone posted
that Google's indexing bots often run in the IP address range
66.249.x.x, I took a look at the ingress filter in amprgw.
66.249.90.x and 66.249.91.x were indeed blocked.
I have unblocked them. Roger, you may see Google crawling your web
site from addresses in those subnets now. If you have some way to
stimulate them to do so, you might want to try that.
I don't know how among many possible ways that those addresses got
on the blocking list, as it was too long ago for the current logs
to reflect it.
- Brian