abuse[at]google.com bounces, google added new in-house abuse address

[Richard7310]

"Tracking link: http://ofslart.ru/agh.html

[report history]

Host ofslart.ru (checking ip) = 8.8.8.8

Resolves to 8.8.8.8

Routing details for 8.8.8.8

[refresh/show] Cached whois for 8.8.8.8 : arin-contact[at]google.com

abuse[at]google.com bounces (99 sent : 118 bounces)

Using best contacts

"No reporting addresses found for 8.8.8.8, using devnull for tracking.

"Reports routes for 8.8.8.8:

routeid: 71895621 8.0.0.0 - 8.255.255.255 to: abuse[at]level3.com

Administrator found from whois records

routeid: 71895620 8.8.8.0 - 8.8.8.255 to: arin-contact[at]google.com

Administrator found from whois records

"Tracking details

Display data:

"whois 8.8.8.8[at]whois.arin.net" (Getting contact from whois.arin.net )

checking NET-8-8-8-0-1

Display data:

"whois NET-8-8-8-0-1[at]whois.arin.net" (Getting contact from whois.arin.net )

Found AbuseEmail in whois arin-contact[at]google.com

8.8.8.0 - 8.8.8.255:arin-contact[at]google.com

checking NET-8-0-0-0-1

Display data:

"whois NET-8-0-0-0-1[at]whois.arin.net" (Getting contact from whois.arin.net )

Found AbuseEmail in whois abuse[at]level3.com

8.0.0.0 - 8.255.255.255:abuse[at]level3.com

Routing details for 8.8.8.8

abuse[at]google.com bounces (99 sent : 118 bounces)

Using best contacts abuse[at]level3.com

_______________________________

3 Mar 2014

However, best contact NOT used because Routing in effect; Routing address not used because of bounces. Concludes No reporting addresses found. May work OK without Routing, though SC does not yet see new google address in current ARIN mirror.

NetRange: 8.0.0.0 - 8.255.255.255

OrgAbuseEmail: abuse[at]level3.com

NetRange: 8.8.8.0 - 8.8.8.255

OrgAbuseEmail: ir-contact-netops-corp[at]google.com

[Farelf]

Aaagh ... agree that's what the resolution of the dns record currently shows, but of course 8.8.8.8 is one of Google's public dns server/resolvers. How come it is also redirected by yandex.ru for ofslart.ru? Something's not right. Feel like we've stepped into an alternate universe here! Can't credit the evidence of my own eyes:

C:\Documents and Settings\Admin>nslookup -type=ns ofslart.ru 8.8.4.4

Server: google-public-dns-b.google.com

Address: 8.8.4.4

Non-authoritative answer:

ofslart.ru nameserver = dns1.yandex.ru

ofslart.ru nameserver = dns2.yandex.ru

Same as (non-authoritative):

C:\Documents and Settings\Admin>nslookup -type=ns ofslart.ru 8.8.8.8

Server: google-public-dns-a.google.com

Address: 8.8.8.8

Non-authoritative answer:

ofslart.ru nameserver = dns2.yandex.ru

ofslart.ru nameserver = dns1.yandex.ru

Confirming (authoritative):

C:\Documents and Settings\Admin>nslookup -type=ns ofslart.ru dns1.yandex.ru

*** Can't find server name for address 213.180.204.213: No information

Server: UnKnown

Address: 213.180.204.213

ofslart.ru nameserver = dns1.yandex.ru

ofslart.ru nameserver = dns2.yandex.ru

Authoritative internet address

C:\Documents and Settings\Admin>nslookup -type=a ofslart.ru dns1.yandex.ru

*** Can't find server name for address 213.180.204.213: No information

Server: UnKnown

Address: 213.180.204.213

Name: ofslart.ru

Address: 8.8.8.8

C:\Documents and Settings\Admin>nslookup -type=a ofslart.ru dns2.yandex.ru

*** Can't find server name for address 93.158.134.213: No information

Server: UnKnown

Address: 93.158.134.213

Name: ofslart.ru

Address: 8.8.8.8

I've broken the live link to ofslart.ru website in above post by the way - that couldn't have been a good thing to support in these pages (though it is, of course, presently unreachable, no port 80 access on 8.8.8.8).

And thanks for pointing out the Google abuse address ...

[Farelf]

Oh, and robtex says "Names pointing to same IP number as ofslart.ru (936 shown) ..." That's 8.8.8.8 and no doubt all or most of those names are with those same yandex.ru name servers. Needless to say, no webhosting service is supported at that address. And we thought the Chinese were out of control ...