BIND-->Route53 Migration

What i understand is you have a domain lets say cloudsolution.com. And this domain have ns records lets say ns1.cloudsolution.com. Your customers are pointing ns record as [login to view URL] as well. So you want to carry your [login to view URL] domain into aws right? You need to create your hosted zone through api with CreateReusableDelegationSet. So that your delegation set will be reusable for every zone you created. Than you will create each zone through api using same delegation set. than you can assign your delegation set ips under [login to view URL] [login to view URL] [login to view URL] [login to view URL] As your customers are pointing out to those, it would work as if you are working on the bind server. But what you ask can only be done only through api, not on web interface. I have used API and written script for many other things in AWS (create instances, change ip etc) but never used them for DNS. Can be done but i cant say i will be done in a hour. It may take time. And please enlighten me about your structure more. So i can say if its doable without any problem.

Hi There Your current BIND server must be up and running In order to keep the name servers intact. Besides I'm clear with the project requirements. It can be done. BTW I'm super expert in AWS. That's my profile where you can view my past AWS experiences. https://www.freelancer.com/u/joystick220.html Thanks Joy

Hi, We help customers do business better by leveraging our industry-wide experience and deep technology expertise. These technology includes setup and management of AWS , different Linux web hosting servers. We are Having expertise in amazon web services. We can setup aws ec2, aws s3 and other amazon products with best configuration. We have expert knowledge of as below techniques:- 1. Amazon Elastic computer cloud(EC2): Virtual servers in a cloud infrastructure We will suggest the instance configuration according to website traffic or resource usage so that unnecessary cost not be beared to client. Security group Management for instance (It works as a firewall in ec2 ) Key pair Management (Authentication Security for instance ,It requires for login) Elastic ip management (dedicated ip to instance) Virtual private Cloud (for private network Management) Volume management on instance AMI (OS image) selection as per application need Upgrade / downgrade of instance resources at run time (without downtime) Snapshot and AMI creation for backup and disaster recovery Load balancer configuration for huge traffic balancing or huge resource balancing , Auto scaling for auto instance creation as per traffic increase or additional resource required Instance health alert Uptime alert setup AWS Identity and Access Management (IAM) users with limited permissions. Amazon user management Region selection for instance as per target audience and for less bandwidth consumption Thank you

Hello! I have right skills and great experience for begin working on your project just right now! You may show good reviews at my profile.

Hi! If you can't change NS-records at DNS registrars then how you will anounce new NS records for zones what will be server by Route53 ? It's compulsory part of migration task.

Hello. All possible in your task except one thing - your customer need to change their nameservers with their domain registrars to route53 DNS server. Without yhis stage migration to route 53 can't be finished.

Hello. Your project is a little complex while we need a write a plan to progressive migration. Route53 is a very robust platform but according your description, you could have some incompatibility problems using your dns servers and route53. I would like work with you for write a plan for your project and finish this task satisfactorily. Best regards and open to questions,.

Your first requirement is not possible buddy. One way or another the registrar have to know what is the domains nameserver. You'll have to contact your clients if you want to migrate over to route 53. Let me know if you have any projects with AWS I can help you with.

Hi, I have been working with DNS servers for the last 2 years. We can update your Route53 servers through cli53 or AXFR. Just we would to make sure does your zonefiles contains complex DNS record types like DNSSec, NSEC etc.

I'm experienced DevOps guy (over 6 years). Worked within the Cloud for integration processes (Amazon web services, Windows Azure, Eucalyptus, CloudStack, and RightScale). Performed DevOps for Linux and Windows platforms. Focused on automation and integration. Monitored developed applications and fixed bugs. Wrote code and designed continual updates. Completed load and performance testing of extremely complex systems. Used PowerShell for DevOps in Windows-based systems. Focused on automation, integration, monitoring and configuration management. Streamlined applications delivery to get applications out to customers faster. Utilized SQL database systems (Mysql, MSSql, Postgresql, Mariadb). Utilized NoSQL database systems (mongodb, Dynomodb, dynamodb). Completed load balancing and proxying of systems, servers and components(HA Proxy/Netscaler, Nginx/Apache/lighttpd, Varnish).Experienced with Interpreted Languages Perl and Python. Understands Compiled languages, C, C++, C#, PHP and JAVA.

I have extensive experience doing mass ISP service migrations after selling my own CLEC/ISP to a competitor that required moving about 1800 zones to various providers. I written quite a few scripts that allow me to format the zone files into a format that can then be used to interface with APIs or used by interactive web applications that post form data. As part of my work flow, I would first validate all zones to ensure they are active and need to be migrated. as well identify any disparities between what the root servers see and what the zone files contain. This would be used to not only migrate the domains but also notify you of any issues that might cause failures or unexpected results.

A proposal has not yet been provided