[196121] in North American Network Operators' Group
Re: Anyone from AT&T DNS?
daemon@ATHENA.MIT.EDU (Jay Farrell via NANOG)
Thu Oct 5 07:52:54 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <41BF05F7-FEF7-45AB-BF43-E30C57D0DB1E@apple.com>
Date: Thu, 5 Oct 2017 04:12:30 -0400
To: Matt Peterman <mpeterman@apple.com>
From: Jay Farrell via NANOG <nanog@nanog.org>
Reply-To: Jay Farrell <jayfar@jayfar.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Yep, the notation with the slash used to be ATT's standard method. At my
job (where we had some customers with ATT MIS T1 circuits) we transitioned
to a web front end for our DNS that didn't allow for the slash, so we had
to nudge ATT to allow us to use a dash notation instead for delegations.
As far as to what can appear in a DNS entry, you'd be amazed. I encountered
a PTR record containing a full URL, http:// and everything; it didn't
actually work of course, but bind allowed it to exist. When I tracked down
the cow-orker who had entered it, he said he knew it wasn't valid, but he
did it that way when the customer insisted it had to be thus. :-D
On Wed, Oct 4, 2017 at 11:33 PM, Matt Peterman <mpeterman@apple.com> wrote:
> I can now confirm that Christopher is right about everything (not that I
> had any doubts! Just wanted to confirm all is working!!)
>
> ATT is now following the RFC (apparently has changed since November 2016
> and June 2017 allocations and DNS changes) and that Route53 WebUI display=
s
> things strangely, however technically works fine on the backend. rDNS is
> now working properly. Thank you Christopher very much! I learned a lot in
> the last hour I can sure say that!
>
> Matt
>
>
>
> > On Oct 4, 2017, at 11:20 PM, Christopher Morrow <morrowc.lists@gmail.co=
m>
> wrote:
> >
> >
> >
> > On Wed, Oct 4, 2017 at 11:18 PM, Matt Peterman <mpeterman@apple.com
> <mailto:mpeterman@apple.com>> wrote:
> > Got it! You=E2=80=99re the winner here. I just setup both of my zones t=
he name
> way and obviously AT&T 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.=E2=
=80=9D It
> changes it to "128\05725.168.207.107.in-addr.arpa.=E2=80=9D every time=E2=
=80=A6 *sigh* If
> it isn't one thing its something else.
> >
> >
> > I've not messed with route53 but fortunately you are treading on well
> trodden ground:
> > https://forums.aws.amazon.com/thread.jspa?messageID=3D674778 <
> https://forums.aws.amazon.com/thread.jspa?messageID=3D674778>
> >
> > have a happy evening! (and I hope that the above works.. again I haven'=
t
> and can't actually try it)
>
>
