Reinhard,
Am 12.09.20 um 16:43 schrieb Reinhard Vicinus:
>>> thanks, for your reply and the information. Sorry for my late reply, but
>>> I had only today time to test. I did try to get the spoa server working
>>> on a ubuntu bionic (18.04.4) with haproxy 2.2.3-2ppa1~bionic from the
>>> vbernat
Tim,
On 9/12/20 4:25 PM, Tim Düsterhus wrote:
> Reinhard,
>
> Am 12.09.20 um 12:45 schrieb Reinhard Vicinus:
>> thanks, for your reply and the information. Sorry for my late reply, but
>> I had only today time to test. I did try to get the spoa server working
>> on a ubuntu bionic (18.04.4) with
Reinhard,
Am 12.09.20 um 12:45 schrieb Reinhard Vicinus:
> thanks, for your reply and the information. Sorry for my late reply, but
> I had only today time to test. I did try to get the spoa server working
> on a ubuntu bionic (18.04.4) with haproxy 2.2.3-2ppa1~bionic from the
> vbernat ppa. I
Tim,
Aleksandar,
On 9/8/20 11:18 PM, Aleksandar Lazic wrote:
> On 08.09.20 22:54, Tim Düsterhus wrote:
>> Reinhard,
>> Björn,
>>
>> Am 08.09.20 um 21:39 schrieb Björn Jacke:
the only official supported way to identify a google bot is to run a
reverse DNS lookup on the accessing IP
On 08.09.20 22:54, Tim Düsterhus wrote:
Reinhard,
Björn,
Am 08.09.20 um 21:39 schrieb Björn Jacke:
the only official supported way to identify a google bot is to run a
reverse DNS lookup on the accessing IP address and run a forward DNS
lookup on the result to verify that it points to
Reinhard,
Björn,
Am 08.09.20 um 21:39 schrieb Björn Jacke:
>> the only official supported way to identify a google bot is to run a
>> reverse DNS lookup on the accessing IP address and run a forward DNS
>> lookup on the result to verify that it points to accessing IP address
>> and the resulting
Hi Reinhard,
On 08.09.20 21:20, Reinhard Vicinus wrote:
> the only official supported way to identify a google bot is to run a
> reverse DNS lookup on the accessing IP address and run a forward DNS
> lookup on the result to verify that it points to accessing IP address
> and the resulting domain
Hi,
the only official supported way to identify a google bot is to run a
reverse DNS lookup on the accessing IP address and run a forward DNS
lookup on the result to verify that it points to accessing IP address
and the resulting domain name is in either googlebot.com or google.com
domain.
As
8 matches
Mail list logo