Since about noon today (7/18), reverse DNS lookups of 44/8 from the outside world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Michael
N6MEF
On 7/18/19 9:46 PM, Michael Fox - N6MEF wrote:
Since about noon today (7/18), reverse DNS lookups of 44/8 from the outside world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Can confirm this is broken for our subnets here in Tampa Bay and AllStar Link across the 5 subnets we're hosted in across the US.
It looks like ARIN has the wrong info for the 44.in-addr.arpa. zone
44.in-addr.arpa. 86400 IN NS r.arin.net. 44.in-addr.arpa. 86400 IN NS x.arin.net. 44.in-addr.arpa. 86400 IN NS z.arin.net. ;; Received 98 bytes from 196.216.169.10#53(196.216.169.10) in 172 ms
44.in-addr.arpa. 10800 IN SOA z.arin.net. dns-ops.arin.net. 2019071804 1800 900 691200 10800 ;; Received 96 bytes from 199.212.0.63#53(199.212.0.63) in 58 ms
Might be a good time to setup DNSSEC too.
I assume it's in some way related to this recent change?
NetRange: 44.192.0.0 - 44.255.255.255 CIDR: 44.192.0.0/10 NetName: AT-88-Z NetHandle: NET-44-192-0-0-1 Parent: NET44 (NET-44-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Amazon Technologies Inc. (AT-88-Z) RegDate: 2019-07-18 Updated: 2019-07-18 Ref: https://rdap.arin.net/registry/ip/44.192.0.0
Regards, Josh VK2HFF
On 19/07/2019 11:46 am, Michael Fox - N6MEF wrote:
Since about noon today (7/18), reverse DNS lookups of 44/8 from the outside world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Michael
N6MEF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
From that whois output I’d conclude that part of 44.0.0.0/8 has been sold to Amazon.
Since it is a /10, some entity somewhere netted upwards of 50 million dollars. Congrats! :-)
Job
On Thu, Jul 18, 2019 at 22:11 Josh josh@festy.org wrote:
I assume it's in some way related to this recent change?
NetRange: 44.192.0.0 - 44.255.255.255 CIDR: 44.192.0.0/10 NetName: AT-88-Z NetHandle: NET-44-192-0-0-1 Parent: NET44 (NET-44-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Amazon Technologies Inc. (AT-88-Z) RegDate: 2019-07-18 Updated: 2019-07-18 Ref: https://rdap.arin.net/registry/ip/44.192.0.0
Regards, Josh VK2HFF
On 19/07/2019 11:46 am, Michael Fox - N6MEF wrote:
Since about noon today (7/18), reverse DNS lookups of 44/8 from the
outside
world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Michael
N6MEF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Guess we can all sell and get our large boats and retire now…
Reverse broken for our BGP subnets as well..
-- Fredric Moses - W8FSM - WQOG498 fred@moses.bz
On Jul 18, 2019, at 22:15, Job Snijders job@ntt.net wrote:
From that whois output I’d conclude that part of 44.0.0.0/8 has been sold to Amazon.
Since it is a /10, some entity somewhere netted upwards of 50 million dollars. Congrats! :-)
Job
Looks like this may have been the plan for quite some time now, surprised we have not heard anything about it from Brian...
https://stat.ripe.net/widget/routing-history#w.resource=AS7377&w.startti...
On Fri, Jul 19, 2019 at 3:16 AM Job Snijders job@ntt.net wrote:
From that whois output I’d conclude that part of 44.0.0.0/8 has been sold to Amazon.
Since it is a /10, some entity somewhere netted upwards of 50 million dollars. Congrats! :-)
Job
On Thu, Jul 18, 2019 at 22:11 Josh josh@festy.org wrote:
I assume it's in some way related to this recent change?
NetRange: 44.192.0.0 - 44.255.255.255 CIDR: 44.192.0.0/10 NetName: AT-88-Z NetHandle: NET-44-192-0-0-1 Parent: NET44 (NET-44-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Amazon Technologies Inc. (AT-88-Z) RegDate: 2019-07-18 Updated: 2019-07-18 Ref: https://rdap.arin.net/registry/ip/44.192.0.0
Regards, Josh VK2HFF
On 19/07/2019 11:46 am, Michael Fox - N6MEF wrote:
Since about noon today (7/18), reverse DNS lookups of 44/8 from the
outside
world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Michael
N6MEF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
In our case, we're in 44.4.50.x, so that's outside of the range below.
M
-----Original Message----- From: 44Net 44net-bounces+n6mef=mefox.org@mailman.ampr.org On Behalf Of Josh Sent: Thursday, July 18, 2019 7:10 PM To: 44net@mailman.ampr.org Subject: Re: [44net] Reverse DNS for 44/8 broken
I assume it's in some way related to this recent change?
NetRange: 44.192.0.0 - 44.255.255.255 CIDR: 44.192.0.0/10 NetName: AT-88-Z NetHandle: NET-44-192-0-0-1 Parent: NET44 (NET-44-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Amazon Technologies Inc. (AT-88-Z) RegDate: 2019-07-18 Updated: 2019-07-18 Ref: https://rdap.arin.net/registry/ip/44.192.0.0
Regards, Josh VK2HFF
On 19/07/2019 11:46 am, Michael Fox - N6MEF wrote:
Since about noon today (7/18), reverse DNS lookups of 44/8 from the outside world have returned NXDOMAIN. Forward DNS works fine.
This is occurring from multiple sites, with multiple service providers.
Michael
N6MEF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Alistair Mackenzie -
Bryan Fields -
Fredric Moses -
Job Snijders -
Josh -
Michael Fox - N6MEF