How to transfer AWS Route 53 domain name to home BIND server
I've been playing around with the idea of hosting my own websites. I've launched a multitude of Ubuntu Servers each with different configurations. My last one was with Plesk installed on it. Pretty neat application.
I have a domain name that is currently residing on Route 53 and I have a public IP from my ISP. I have both port 80 and 443 forwarded to my static internal IP. My website is always accessible from the internet but only using my external IP address.
How do I point the DNS servers to my own if I install BIND on Ubuntu 16.04 LTS? I already tried pointing my Route 53 IP address to my external IP but that didn't work. There is also a Transfer Lock on the registered domains page. Do I unlock it?
16.04 aws bind
asked Dec 11 at 23:24
Kimosabe2016
94
add a comment |
I've been playing around with the idea of hosting my own websites. I've launched a multitude of Ubuntu Servers each with different configurations. My last one was with Plesk installed on it. Pretty neat application.
I have a domain name that is currently residing on Route 53 and I have a public IP from my ISP. I have both port 80 and 443 forwarded to my static internal IP. My website is always accessible from the internet but only using my external IP address.
How do I point the DNS servers to my own if I install BIND on Ubuntu 16.04 LTS? I already tried pointing my Route 53 IP address to my external IP but that didn't work. There is also a Transfer Lock on the registered domains page. Do I unlock it?
16.04 aws bind
asked Dec 11 at 23:24
Kimosabe2016
94
add a comment |
I've been playing around with the idea of hosting my own websites. I've launched a multitude of Ubuntu Servers each with different configurations. My last one was with Plesk installed on it. Pretty neat application.
I have a domain name that is currently residing on Route 53 and I have a public IP from my ISP. I have both port 80 and 443 forwarded to my static internal IP. My website is always accessible from the internet but only using my external IP address.
How do I point the DNS servers to my own if I install BIND on Ubuntu 16.04 LTS? I already tried pointing my Route 53 IP address to my external IP but that didn't work. There is also a Transfer Lock on the registered domains page. Do I unlock it?
16.04 aws bind
asked Dec 11 at 23:24
Kimosabe2016
94
I've been playing around with the idea of hosting my own websites. I've launched a multitude of Ubuntu Servers each with different configurations. My last one was with Plesk installed on it. Pretty neat application.
I have a domain name that is currently residing on Route 53 and I have a public IP from my ISP. I have both port 80 and 443 forwarded to my static internal IP. My website is always accessible from the internet but only using my external IP address.
How do I point the DNS servers to my own if I install BIND on Ubuntu 16.04 LTS? I already tried pointing my Route 53 IP address to my external IP but that didn't work. There is also a Transfer Lock on the registered domains page. Do I unlock it?
16.04 aws bind
16.04 aws bind
asked Dec 11 at 23:24
Kimosabe2016
94
asked Dec 11 at 23:24
Kimosabe2016
94
asked Dec 11 at 23:24
Kimosabe2016
94
asked Dec 11 at 23:24
Kimosabe2016
94
asked Dec 11 at 23:24
Kimosabe2016
94
94
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Pointing your domain name to home IP should totally work in your scenario.
See if you can troubleshoot it, you need to only update A records and possibly www CNAME to use that public IP from your ISP.
If you absolutely must move from Route 53, you still won't be able to do properly using a single IP you have at home: usually, DNS zone needs at least two NS servers with different IP addresses (more information here: https://www.iana.org/help/nameserver-requirements)
answered Dec 11 at 23:55
Gleb Reys
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100169%2fhow-to-transfer-aws-route-53-domain-name-to-home-bind-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Pointing your domain name to home IP should totally work in your scenario.
See if you can troubleshoot it, you need to only update A records and possibly www CNAME to use that public IP from your ISP.
If you absolutely must move from Route 53, you still won't be able to do properly using a single IP you have at home: usually, DNS zone needs at least two NS servers with different IP addresses (more information here: https://www.iana.org/help/nameserver-requirements)
answered Dec 11 at 23:55
Gleb Reys
11
add a comment |
Pointing your domain name to home IP should totally work in your scenario.
See if you can troubleshoot it, you need to only update A records and possibly www CNAME to use that public IP from your ISP.
If you absolutely must move from Route 53, you still won't be able to do properly using a single IP you have at home: usually, DNS zone needs at least two NS servers with different IP addresses (more information here: https://www.iana.org/help/nameserver-requirements)
answered Dec 11 at 23:55
Gleb Reys
11
add a comment |
Pointing your domain name to home IP should totally work in your scenario.
See if you can troubleshoot it, you need to only update A records and possibly www CNAME to use that public IP from your ISP.
If you absolutely must move from Route 53, you still won't be able to do properly using a single IP you have at home: usually, DNS zone needs at least two NS servers with different IP addresses (more information here: https://www.iana.org/help/nameserver-requirements)
answered Dec 11 at 23:55
Gleb Reys
11
Pointing your domain name to home IP should totally work in your scenario.
See if you can troubleshoot it, you need to only update A records and possibly www CNAME to use that public IP from your ISP.
If you absolutely must move from Route 53, you still won't be able to do properly using a single IP you have at home: usually, DNS zone needs at least two NS servers with different IP addresses (more information here: https://www.iana.org/help/nameserver-requirements)
answered Dec 11 at 23:55
Gleb Reys
11
answered Dec 11 at 23:55
Gleb Reys
11
answered Dec 11 at 23:55
Gleb Reys
11
answered Dec 11 at 23:55
Gleb Reys
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100169%2fhow-to-transfer-aws-route-53-domain-name-to-home-bind-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
