invalid prefixlen in publicdns.json [270231429]

Assigned

Customer Issue

Status Update

No update yet.

Description

ki...@gmail.com

created issue #1

Feb 22, 2023 02:40PM

☑️ I affirm that I have looked at all the other public issue templates at https://issuetracker.google.com/components/191657/manage#templates and restricted issue templates at https://issuetracker.google.com/components/191885/manage#templates and none of them apply.

https://www.gstatic.com/ipranges/publicdns.json linked from a support page has invalid prefix length. The other multiple versions have the similar mistakes.

version:

  "syncToken": "1677069559",
  "creationTime": "2023-02-22T12:39:19.000Z",

Example 1: 74.125.16.160/26 is invalid. A bit is 1 in the host part.

    {
      "ipv4Prefix": "74.125.16.160/26",
      "service": "Google Public DNS",
      "scope": "bom"
    },

Example 2: 2404:6800:4000:1015::100/48 is invalid. Some bits are 1 in the host part.

    {
      "ipv6Prefix": "2404:6800:4000:1015::100/48",
      "service": "Google Public DNS",
      "scope": "bom"
    },

At least std::net::Ipv4Addr / std::net::Ipv6Addr in Rust rejects these invalid prefixes. It causes parsing publicdns.json to fail and unusable.

Can you correct these prefixes?

Comments

ki...@gmail.com <ki...@gmail.com> #2Feb 22, 2023 02:58PM

Automated by Blunderbuss job honestdns_tickets_blunderbuss_autoassigner for 2nd config honestdns_defects_customer_issues for component 191657.

ch...@google.com <ch...@google.com> Feb 24, 2023 03:14PM

Assigned to wa...@google.com.

wa...@google.com <wa...@google.com> May 7, 2024 07:08PM

Reassigned to st...@google.com.

st...@google.com <st...@google.com> Aug 7, 2024 07:11PM

Status: New

bl...@google.com <bl...@google.com> #3Oct 15, 2024 01:51PM

Assigned to pu...@google.com.

Hello, We are reviewing your request and need to verify it is from the organization which owns this address block. I have reached out to the owner of the address block, e.zuniga@libertycr.com, for verification.

Alternatively, if you can reply or send me an email from j.medrano@libertycr.com or ja.benavides@libertycr.com. This would allow us to move to the next steps.

Thanks!

pu...@google.com <pu...@google.com> #4Oct 16, 2024 06:42AM

Hello

We have already answered the email with the mail j.medrano@libertycr.com

Thank you for contacting us.

Let's continue the process from the other email account.

Regards

bl...@google.com <bl...@google.com> #5Jan 14, 2025 01:11PM

Yes, I heard back from j.medrano@libertycr.com confirming this request.

We've moved forward with this request and the changes (increasing client QPS to 5,000) will roll out next week.