[AusNOG] AWS Support

Giles Pollock glp71s at gmail.com
Tue Jul 19 19:12:46 EST 2016

Someone will be paying for the AWS account, which should get you started in
terms of account number with AWS. As for administering Route53, yep, this
needs to be done through the console, or via powershell and/or r53cli (if
you're feeling adventurous). Either way you will need access to the AWS
account the zones are hosted in...

Giles Pollock
(I spend far too much time looking at Route53)

On Tue, Jul 19, 2016 at 4:16 PM, Jason Firmino <jason.firmino at gmail.com>

> Hi Paul,
> For what I understand you don't have access to the AWS console where that
> domain is registered.
> If you want to make any DNS changes someone needs to find those
> credentials, otherwise I don't see how you're gonna do it.
> As a last resort (and I don't think it's the best approach), the client
> goes to his domain registrar and changes his NS records to another route
> 53/DNS provider's Name Servers.
> Good luck.
> Cheers,
> Jason
> On Tue, 19 Jul 2016 at 16:02 Paul Walters <paul.walters at walthome.com>
> wrote:
>> Afternoon All,
>> I have a bit of a tricky one. I have a client who has their DNS hosted
>> with Route 53. The client has changed a few IT providers they don't know
>> which account was setup (seems that it wasn't a generic admin@)
>> Is anyone able to point me to someone or something that might be able to
>> get me access to their DNS to make some adjustments?
>> Thanks in advanced
>> Paul
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20160719/c609fb75/attachment.html>

More information about the AusNOG mailing list