Re: Anyone from AT DNS?

2017-10-08 Thread Mark Andrews 

In message

Re: Anyone from AT DNS?

2017-10-08 Thread Mark Andrews 

In message <50298399-672d-4ba1-a726-7128b84b8...@apple.com>, Matt Peterman 
writes:
> Got it! You’re the winner here. I just setup both of my zones the name
> way and obviously AT changed the way they did RDNS entries from when I
> got a /25 last November and this second /25 in June. Oh well!
>
> Now I am running into the challenge of Route53 does seem to support
> creating an authoritative zone for "128/25.168.207.107.in-addr.arpa.” It
> changes it to "128\05725.168.207.107.in-addr.arpa.” every time… *sigh* If
> it isn't one thing its something else.

Which is "128925.168.207.107.in-addr.arpa." when fed into a domain
name parser.  DNS escapes sequences are DECIMAL not OCTAL.  I suggest
that you log a bug report.

128/25.168.207.107.in-addr.arpa. == 128\04725.168.207.107.in-addr.arpa

RFC 1035

\DDDwhere each D is a digit is the octet corresponding to
the decimal number described by DDD.  The resulting
octet is assumed to be text and is not checked for
special meaning.

That said '/' is not special to DNS parsers and shouldn't need to be
converted to \DDD.

Mark

% dig '128\05725.168.207.107.in-addr.arpa'
;; BADCOOKIE, retrying.

; <<>> DiG 9.12.0a1+hotspot+add-prefetch+marka <<>> 
128\05725.168.207.107.in-addr.arpa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8078
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: ac2bc18c4e18f907a872f2b559dacb6ab6e64fb72a9c71d5 (good)
;; QUESTION SECTION:
;128925.168.207.107.in-addr.arpa. INA

;; AUTHORITY SECTION:
168.207.107.in-addr.arpa. 3600  IN  SOA ns1.swbell.net. 
rm-hostmaster.ems.att.com. 2 10800 900 604800 7200

;; Query time: 1244 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Oct 09 12:05:46 AEDT 2017
;; MSG SIZE  rcvd: 163

% 

% dig '128\04725.168.207.107.in-addr.arpa'
;; BADCOOKIE, retrying.

; <<>> DiG 9.12.0a1+hotspot+add-prefetch+marka <<>> 
128\04725.168.207.107.in-addr.arpa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54452
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: e6bdbbdf26697275cf492e9059dacbecc9eb8186d940bd69 (good)
;; QUESTION SECTION:
;128/25.168.207.107.in-addr.arpa. INA

;; AUTHORITY SECTION:
128/25.168.207.107.in-addr.arpa. 900 IN SOA ns-1746.awsdns-26.co.uk. 
awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 1142 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Oct 09 12:07:56 AEDT 2017
;; MSG SIZE  rcvd: 175

% 

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: Hurricane Maria: Summary of communication status - and lack of

2017-10-08 Thread Mike Hammett 
>From a WISP in USVI

A quick perspective from the US Virgin Islands of how the carriers have fared / 
performed:

AT = had a couple towers with some cell coverage after Irma and Maria.  A 
testament to good engineering at the tower, and redundancy in their network 
design.  Primarily microwave backhaul, but leasing some fiber from the ILEC 
named Viya.  AT has a major undersea cable station and POP on STT in downtown 
Charlotte Amalie.  They have been making progress fixing their network, STX is 
over 50% fixed 2 weeks after Maria.  75% market share

Sprint = 100% down for the 3+ weeks after Irma.  They have a single point of 
failure, relying on 10ft dishes to shoot 20-50 miles, from STT to Puerto Rico.  
These cheap bastards wouldn’t buy a backup connection from Viya or Broadband 
VI.  I have called them out to the PSC.  Still weeks away from anything 
working.  Most of their customers can roam on Viya’s cell  network.  15% market 
share and rapidly declining.

Viya = Celluar = 30-50% up, Celluar  = 10% market share.  Rolling out LTE 
upgrade.
Cable TV/Phone/Internet = 10% up, 75% market share, have a long road to 
recovery.  Have to wait for power company poles to be replaced / fixed before 
they can repair their badly damaged plant.

Broadband VI = WISP = 50% AP's up, 15% of customers.  Got up quickly after 
Irma, STX stayed up, STT had backhaul to every major tower repaired in 5 days.  
After Maria 100% down.  Had to re-aim / repair every major tower on STX, and 
most of STT.  Moving focus from backhaul to repairing AP’s next week.  Tower by 
tower, with installers / subs going to customers in that area (who have power, 
almost all via generator).  In the middle of a Mikrotik 2 Cambium 450 forklift 
upgrade.  Impressive survival rate for Cambium AP’s, and Ceragon IP-20.  
 
viNGN = Government fiber middle-mile, lost 90% of their drops because there 
were aerial.

I am off to guide the FEMA re-fuelers to a remote tower which ran out of fuel 
last night. 
There have been some lessons learned.  I will compile a report in the next few 
weeks.  

Mike Meluskey
CTO and Founder
Broadband VI



-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

Midwest-IX
http://www.midwest-ix.com

- Original Message -
From: Javier J 
To: Jean-Francois Mezei 
Cc: nanog@nanog.org
Sent: Sat, 07 Oct 2017 03:02:46 -0500 (CDT)
Subject: Re: Hurricane Maria: Summary of communication status - and lack of

@ Jean

Interesting stuff. Please keep this thread updated with info on that
initiative.

On Fri, Oct 6, 2017 at 9:55 PM, Jean-Francois Mezei <
jfmezei_na...@vaxination.ca> wrote:

> I have not ound the official announcements, but the press is reporting
> that the FCC has granted Google rights to fly 30 of its "Loon" high
> altitude ballons to provide cellular cervice in Puerto Rico for up to 6
> months.
>
> (From my readings, there are glorified relays of ground based signals
> (which I assume some antennas have to be oriented to face up towards the
> balloons).
>
> The Loon will use spectrum allocated to the carriers they relay (and got
> their OK)
>
> Altitude 20km. (so not sure they need 30 balloons, 1 probably suffices
> to cover all of PR).
>
> I suspect more concrete info will be coming.
>