[196120] in North American Network Operators' Group
Re: Anyone from AT&T DNS?
daemon@ATHENA.MIT.EDU (Matt Peterman)
Thu Oct 5 07:52:54 2017
X-Original-To: nanog@nanog.org
From: Matt Peterman <mpeterman@apple.com>
Date: Wed, 04 Oct 2017 23:33:00 -0400
In-reply-to: <CAL9jLaaTcpsAu15GNKBnGO1qpURWpUWXz6y87tW7hQ-XP-9WTg@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I can now confirm that Christopher is right about everything (not that I =
had any doubts! Just wanted to confirm all is working!!)=20
ATT is now following the RFC (apparently has changed since November 2016 =
and June 2017 allocations and DNS changes) and that Route53 WebUI =
displays 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!=20
Matt
> On Oct 4, 2017, at 11:20 PM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
>=20
>=20
>=20
> 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 =
the 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!
>=20
> 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.=20
>=20
>=20
> 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>
>=20
> have a happy evening! (and I hope that the above works.. again I =
haven't and can't actually try it)
