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 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! Matt > On Oct 4, 2017, at 11:20 PM, Christopher Morrow <morrowc.li...@gmail.com> > wrote: > > > > On Wed, Oct 4, 2017 at 11:18 PM, Matt Peterman <mpeter...@apple.com > <mailto:mpeter...@apple.com>> wrote: > Got it! You’re 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! > > 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. > > > I've not messed with route53 but fortunately you are treading on well trodden > ground: > https://forums.aws.amazon.com/thread.jspa?messageID=674778 > <https://forums.aws.amazon.com/thread.jspa?messageID=674778> > > have a happy evening! (and I hope that the above works.. again I haven't and > can't actually try it)
