Google PTR?

Mailman List Mirror (Read Only)
1

I'm sure I'm bringing up a topic that's been brought up before, but I
figured I'd have a go.

Anyone from Google around that could answer to why there is no reverse
DNS/PTR with most Google IP addresses (from traceroute, etc)?

Alternatively, is there a server that can be utilized by the net operators
community to at least get an answer on some of the IPs?

It's very frustrating to contend with no PTR records in traces for
troubleshooting and the like.

Any information (off list or on) would be greatly appreciated.

Thanks,
Blair Trosper
Updraft Networks & North Texas GigaPOP

2

Which particular address are you referring to?
I get PTR responses for the limited set of address I get from google.

such as
den03s06-in-x14.1e100.net [2607:f8b0:400f:801::1014]

3

examples are good... I suspect he means things inside 15169's network
that are not serving external people services: 209.85.243.114

for instance?

4

Hi Blair

I guess that's pretty much because they don't really wish to put any info
related to routers in public including location & circuit bandwidth which
is often given major networks in PTR.

Btw I guess you must be troubleshooting some routing issue. My experience
has been decent with them in past. They are usually responsive on the email
addresses mentioned in peering db for AS15169.

http://www.peeringdb.com/view.php?asn=15169

5

Hi Blair

I guess that's pretty much because they don't really wish to put any info
related to routers in public including location & circuit bandwidth which is
often given major networks in PTR.

more over, what help is it? I'm of two minds really about this:
1) it's handy to say: the router in elbonia is being 'bad'
2) it's just as simple to say: 'your router with interface ip 1.2.3.4
is being bad'
     (or: "everything through 1.2.3.4 is forked... plstofixkthxbi!")

It's often cited as a headache to maintain the PTRs (not really,
automation ftw!) I think really it gets down to "how does it really
help?"

Btw I guess you must be troubleshooting some routing issue. My experience
has been decent with them in past. They are usually responsive on the email
addresses mentioned in peering db for AS15169.

also folk watch this list (and others)...though certainly the proper
contact method is that which is in peeringdb.

6

It's often cited as a headache to maintain the PTRs (not really,
automation ftw!) I think really it gets down to "how does it really
help?"

why is my traffic between seattle and new york going through tokyo?

randy

7

'because someone forgot to rename the ptr' ?

8

'because it's the mid-2000s and I'm using ipv6?'

9

Hi Blair

I guess that's pretty much because they don't really wish to put any info
related to routers in public including location & circuit bandwidth which is
often given major networks in PTR.

more over, what help is it? I'm of two minds really about this:
1) it's handy to say: the router in elbonia is being 'bad'
2) it's just as simple to say: 'your router with interface ip 1.2.3.4
is being bad'
    (or: "everything through 1.2.3.4 is forked... plstofixkthxbi!")

True, but...

It's handy to say foo-e1-kcks is hosed.
Not as handy to say 2001:db8:5fe3:139a:6254:03ff:fe19:acf3 is hosed.

It's often cited as a headache to maintain the PTRs (not really,
automation ftw!) I think really it gets down to "how does it really
help?"

See above? Beyond that, it's also convenient if you're trying to correlate outages
affecting more than just google. For example, if I'm getting complaints about
access to google, yahoo, nymex, and edgar and traceroutes to all three of those
show packet loss between routers in Dallas and routers in Atlanta, then I know
I'm probably facing a fiber or carrier outage or partial outage along the Dallas
to Atlanta path. I may be able to take independent action to reroute my traffic
via a more northerly path to avoid that problem.

Owen