How to export a hosted zone in AWS Route 53? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Should we host our own nameservers?Create 301 Redirection in Amazon Route 53 for Wildcard SubdomainsDig -x equivalent for AWS Route 53AWS CloudFormation Create Route 53 Private Hosted ZoneAWS: Route 53 Configurationsubdomain on route53 private hosted Zonesub-subdomain records for public hosted zone in AWS not workingDNS isues with AWS Route53 hosted zone / nameserversAWS Route 53 and Certificate managerMigration from GoDaddy to AWS Route 53: domain lost
Problem when applying foreach loop
Aligning matrix of nodes with grid
What did Darwin mean by 'squib' here?
Single author papers against my advisor's will?
Direct Experience of Meditation
Cold is to Refrigerator as warm is to?
What would be Julian Assange's expected punishment, on the current English criminal law?
I'm thinking of a number
How do I automatically answer y in bash script?
Am I ethically obligated to go into work on an off day if the reason is sudden?
Can't figure this one out.. What is the missing box?
What to do with post with dry rot?
If A makes B more likely then B makes A more likely"
Passing functions in C++
Do working physicists consider Newtonian mechanics to be "falsified"?
Estimated State payment too big --> money back; + 2018 Tax Reform
Would an alien lifeform be able to achieve space travel if lacking in vision?
Interesting examples of non-locally compact topological groups
How did the aliens keep their waters separated?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
How is simplicity better than precision and clarity in prose?
How to market an anarchic city as a tourism spot to people living in civilized areas?
What are the performance impacts of 'functional' Rust?
Classification of bundles, Postnikov towers, obstruction theory, local coefficients
How to export a hosted zone in AWS Route 53?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Should we host our own nameservers?Create 301 Redirection in Amazon Route 53 for Wildcard SubdomainsDig -x equivalent for AWS Route 53AWS CloudFormation Create Route 53 Private Hosted ZoneAWS: Route 53 Configurationsubdomain on route53 private hosted Zonesub-subdomain records for public hosted zone in AWS not workingDNS isues with AWS Route53 hosted zone / nameserversAWS Route 53 and Certificate managerMigration from GoDaddy to AWS Route 53: domain lost
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I see no option to export a backup of the settings for a domain.
Maybe I should save the results of public DNS with dig but I would question whether a friend knows a better way.
domain-name-system amazon-web-services amazon-route53
add a comment |
I see no option to export a backup of the settings for a domain.
Maybe I should save the results of public DNS with dig but I would question whether a friend knows a better way.
domain-name-system amazon-web-services amazon-route53
add a comment |
I see no option to export a backup of the settings for a domain.
Maybe I should save the results of public DNS with dig but I would question whether a friend knows a better way.
domain-name-system amazon-web-services amazon-route53
I see no option to export a backup of the settings for a domain.
Maybe I should save the results of public DNS with dig but I would question whether a friend knows a better way.
domain-name-system amazon-web-services amazon-route53
domain-name-system amazon-web-services amazon-route53
asked Sep 2 '13 at 11:39
gpupogpupo
4352711
4352711
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
Yes, it can be more friendly way. I suggest using cli53 tool, https://github.com/barnybug/cli53
After you setup it, just try
cli53 export --full sciworth.com
And you get the export zone in bind format.
add a comment |
No need of additional software installations. You need only awscli.
Here is what I just wrote. It is simple and works like charm.
#!/bin/bash -e
#
# Author: Peycho Dimitrov
#
# DESCRIPTION
#
# Create full backup of all hosted Route53 zones / domains in your account.
#
# REQUIREMENTS
#
# Available s3 bucket (where your json files will be saved)
# awscli (with cofigured credentials or IAM role)
# gzip
# awk
#
####################################
# CONFIGURATION
region="us-east-1" # Your aws region
b_route53_tmp="/tmp/r53_backup" # Your temp directory
b_route53_bucket="s3://my-backups/route53" # Your backup folder in s3.
# END OF CONFIGURATION
# Do not edit here if you don't know what your're doing! #
mkdir -p $b_route53_tmp
echo "$(date) Backup all Route53 zones and resource records."
p_aws="$(which aws) --region $region"
r53_zones=$($p_aws route53 list-hosted-zones --query '[HostedZones[*].[Id, Name]]' --output text | awk -F'/' 'print $3')
if [ ! -z "$r53_zones" ]; then
while read route; do
zone=$(echo "$route" | awk 'print $1')
domain=$(echo "$route" | awk 'print $2')
echo "Processing $zone / $domain"
$p_aws route53 list-resource-record-sets --hosted-zone-id "$zone" --output json > "$b_route53_tmp"/$(date +%Y%m%d%H%M%S)-"$zone"-"$domain"backup.json
done <<<"$r53_zones"
echo "Archive json files."
gzip "$b_route53_tmp"/*backup.json
echo "Backup $zone / $domain data to $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/"
$p_aws s3 cp "$b_route53_tmp"/ $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/ --exclude "*" --include "*.gz" --recursive
fi
echo "$(date) Done!"
add a comment |
If you want to export to bind format, you can use this script:
#!/bin/bash
zonename=$1
hostedzoneid=$(aws route53 list-hosted-zones | jq -r ".HostedZones[] | select(.Name == "$zonename.") | .Id" | cut -d'/' -f3)
aws route53 list-resource-record-sets --hosted-zone-id $hostedzoneid --output json | jq -jr '.ResourceRecordSets[] | "(.Name) t(.TTL) t(.Type) t(.ResourceRecords[].Value)n"'
add a comment |
To export a hosted zone in AWS Route 53, follow these steps (let say you are using example.com hosted zone):
Step 1: Installation – pip install route53-transfer
Step 2: Backup the zone to a CSV file:
route53-transfer dump example.com backup.csv
Use STDOUT instead of a file
route53-transfer dump example.com –
Step 3: Restore a zone:
route53-transfer load example.com backup.csv
Use - to load from STDIN instead
Migrate between accounts:
Use command line switches for overriding the access and secret keys:
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com
route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
If you are working with private zones, use –private to distinguish private domains:
route53-transfer --private dump example.com example-private.csv
route53-transfer dump example.com example-public.csv
add a comment |
You can sign up for Cloudflare.com and add a free website.
Cloudflare will scan your DNS as part of its onboarding.
After import (or maybe during), in "Advanced" below the DNS records, there is an Export DNS file button.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f535631%2fhow-to-export-a-hosted-zone-in-aws-route-53%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, it can be more friendly way. I suggest using cli53 tool, https://github.com/barnybug/cli53
After you setup it, just try
cli53 export --full sciworth.com
And you get the export zone in bind format.
add a comment |
Yes, it can be more friendly way. I suggest using cli53 tool, https://github.com/barnybug/cli53
After you setup it, just try
cli53 export --full sciworth.com
And you get the export zone in bind format.
add a comment |
Yes, it can be more friendly way. I suggest using cli53 tool, https://github.com/barnybug/cli53
After you setup it, just try
cli53 export --full sciworth.com
And you get the export zone in bind format.
Yes, it can be more friendly way. I suggest using cli53 tool, https://github.com/barnybug/cli53
After you setup it, just try
cli53 export --full sciworth.com
And you get the export zone in bind format.
answered Sep 2 '13 at 13:44
astlockastlock
66948
66948
add a comment |
add a comment |
No need of additional software installations. You need only awscli.
Here is what I just wrote. It is simple and works like charm.
#!/bin/bash -e
#
# Author: Peycho Dimitrov
#
# DESCRIPTION
#
# Create full backup of all hosted Route53 zones / domains in your account.
#
# REQUIREMENTS
#
# Available s3 bucket (where your json files will be saved)
# awscli (with cofigured credentials or IAM role)
# gzip
# awk
#
####################################
# CONFIGURATION
region="us-east-1" # Your aws region
b_route53_tmp="/tmp/r53_backup" # Your temp directory
b_route53_bucket="s3://my-backups/route53" # Your backup folder in s3.
# END OF CONFIGURATION
# Do not edit here if you don't know what your're doing! #
mkdir -p $b_route53_tmp
echo "$(date) Backup all Route53 zones and resource records."
p_aws="$(which aws) --region $region"
r53_zones=$($p_aws route53 list-hosted-zones --query '[HostedZones[*].[Id, Name]]' --output text | awk -F'/' 'print $3')
if [ ! -z "$r53_zones" ]; then
while read route; do
zone=$(echo "$route" | awk 'print $1')
domain=$(echo "$route" | awk 'print $2')
echo "Processing $zone / $domain"
$p_aws route53 list-resource-record-sets --hosted-zone-id "$zone" --output json > "$b_route53_tmp"/$(date +%Y%m%d%H%M%S)-"$zone"-"$domain"backup.json
done <<<"$r53_zones"
echo "Archive json files."
gzip "$b_route53_tmp"/*backup.json
echo "Backup $zone / $domain data to $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/"
$p_aws s3 cp "$b_route53_tmp"/ $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/ --exclude "*" --include "*.gz" --recursive
fi
echo "$(date) Done!"
add a comment |
No need of additional software installations. You need only awscli.
Here is what I just wrote. It is simple and works like charm.
#!/bin/bash -e
#
# Author: Peycho Dimitrov
#
# DESCRIPTION
#
# Create full backup of all hosted Route53 zones / domains in your account.
#
# REQUIREMENTS
#
# Available s3 bucket (where your json files will be saved)
# awscli (with cofigured credentials or IAM role)
# gzip
# awk
#
####################################
# CONFIGURATION
region="us-east-1" # Your aws region
b_route53_tmp="/tmp/r53_backup" # Your temp directory
b_route53_bucket="s3://my-backups/route53" # Your backup folder in s3.
# END OF CONFIGURATION
# Do not edit here if you don't know what your're doing! #
mkdir -p $b_route53_tmp
echo "$(date) Backup all Route53 zones and resource records."
p_aws="$(which aws) --region $region"
r53_zones=$($p_aws route53 list-hosted-zones --query '[HostedZones[*].[Id, Name]]' --output text | awk -F'/' 'print $3')
if [ ! -z "$r53_zones" ]; then
while read route; do
zone=$(echo "$route" | awk 'print $1')
domain=$(echo "$route" | awk 'print $2')
echo "Processing $zone / $domain"
$p_aws route53 list-resource-record-sets --hosted-zone-id "$zone" --output json > "$b_route53_tmp"/$(date +%Y%m%d%H%M%S)-"$zone"-"$domain"backup.json
done <<<"$r53_zones"
echo "Archive json files."
gzip "$b_route53_tmp"/*backup.json
echo "Backup $zone / $domain data to $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/"
$p_aws s3 cp "$b_route53_tmp"/ $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/ --exclude "*" --include "*.gz" --recursive
fi
echo "$(date) Done!"
add a comment |
No need of additional software installations. You need only awscli.
Here is what I just wrote. It is simple and works like charm.
#!/bin/bash -e
#
# Author: Peycho Dimitrov
#
# DESCRIPTION
#
# Create full backup of all hosted Route53 zones / domains in your account.
#
# REQUIREMENTS
#
# Available s3 bucket (where your json files will be saved)
# awscli (with cofigured credentials or IAM role)
# gzip
# awk
#
####################################
# CONFIGURATION
region="us-east-1" # Your aws region
b_route53_tmp="/tmp/r53_backup" # Your temp directory
b_route53_bucket="s3://my-backups/route53" # Your backup folder in s3.
# END OF CONFIGURATION
# Do not edit here if you don't know what your're doing! #
mkdir -p $b_route53_tmp
echo "$(date) Backup all Route53 zones and resource records."
p_aws="$(which aws) --region $region"
r53_zones=$($p_aws route53 list-hosted-zones --query '[HostedZones[*].[Id, Name]]' --output text | awk -F'/' 'print $3')
if [ ! -z "$r53_zones" ]; then
while read route; do
zone=$(echo "$route" | awk 'print $1')
domain=$(echo "$route" | awk 'print $2')
echo "Processing $zone / $domain"
$p_aws route53 list-resource-record-sets --hosted-zone-id "$zone" --output json > "$b_route53_tmp"/$(date +%Y%m%d%H%M%S)-"$zone"-"$domain"backup.json
done <<<"$r53_zones"
echo "Archive json files."
gzip "$b_route53_tmp"/*backup.json
echo "Backup $zone / $domain data to $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/"
$p_aws s3 cp "$b_route53_tmp"/ $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/ --exclude "*" --include "*.gz" --recursive
fi
echo "$(date) Done!"
No need of additional software installations. You need only awscli.
Here is what I just wrote. It is simple and works like charm.
#!/bin/bash -e
#
# Author: Peycho Dimitrov
#
# DESCRIPTION
#
# Create full backup of all hosted Route53 zones / domains in your account.
#
# REQUIREMENTS
#
# Available s3 bucket (where your json files will be saved)
# awscli (with cofigured credentials or IAM role)
# gzip
# awk
#
####################################
# CONFIGURATION
region="us-east-1" # Your aws region
b_route53_tmp="/tmp/r53_backup" # Your temp directory
b_route53_bucket="s3://my-backups/route53" # Your backup folder in s3.
# END OF CONFIGURATION
# Do not edit here if you don't know what your're doing! #
mkdir -p $b_route53_tmp
echo "$(date) Backup all Route53 zones and resource records."
p_aws="$(which aws) --region $region"
r53_zones=$($p_aws route53 list-hosted-zones --query '[HostedZones[*].[Id, Name]]' --output text | awk -F'/' 'print $3')
if [ ! -z "$r53_zones" ]; then
while read route; do
zone=$(echo "$route" | awk 'print $1')
domain=$(echo "$route" | awk 'print $2')
echo "Processing $zone / $domain"
$p_aws route53 list-resource-record-sets --hosted-zone-id "$zone" --output json > "$b_route53_tmp"/$(date +%Y%m%d%H%M%S)-"$zone"-"$domain"backup.json
done <<<"$r53_zones"
echo "Archive json files."
gzip "$b_route53_tmp"/*backup.json
echo "Backup $zone / $domain data to $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/"
$p_aws s3 cp "$b_route53_tmp"/ $b_route53_bucket/$(date +%Y)/$(date +%m)/$(date +%d)/ --exclude "*" --include "*.gz" --recursive
fi
echo "$(date) Done!"
answered Jul 14 '16 at 15:48
Peycho DimitrovPeycho Dimitrov
45848
45848
add a comment |
add a comment |
If you want to export to bind format, you can use this script:
#!/bin/bash
zonename=$1
hostedzoneid=$(aws route53 list-hosted-zones | jq -r ".HostedZones[] | select(.Name == "$zonename.") | .Id" | cut -d'/' -f3)
aws route53 list-resource-record-sets --hosted-zone-id $hostedzoneid --output json | jq -jr '.ResourceRecordSets[] | "(.Name) t(.TTL) t(.Type) t(.ResourceRecords[].Value)n"'
add a comment |
If you want to export to bind format, you can use this script:
#!/bin/bash
zonename=$1
hostedzoneid=$(aws route53 list-hosted-zones | jq -r ".HostedZones[] | select(.Name == "$zonename.") | .Id" | cut -d'/' -f3)
aws route53 list-resource-record-sets --hosted-zone-id $hostedzoneid --output json | jq -jr '.ResourceRecordSets[] | "(.Name) t(.TTL) t(.Type) t(.ResourceRecords[].Value)n"'
add a comment |
If you want to export to bind format, you can use this script:
#!/bin/bash
zonename=$1
hostedzoneid=$(aws route53 list-hosted-zones | jq -r ".HostedZones[] | select(.Name == "$zonename.") | .Id" | cut -d'/' -f3)
aws route53 list-resource-record-sets --hosted-zone-id $hostedzoneid --output json | jq -jr '.ResourceRecordSets[] | "(.Name) t(.TTL) t(.Type) t(.ResourceRecords[].Value)n"'
If you want to export to bind format, you can use this script:
#!/bin/bash
zonename=$1
hostedzoneid=$(aws route53 list-hosted-zones | jq -r ".HostedZones[] | select(.Name == "$zonename.") | .Id" | cut -d'/' -f3)
aws route53 list-resource-record-sets --hosted-zone-id $hostedzoneid --output json | jq -jr '.ResourceRecordSets[] | "(.Name) t(.TTL) t(.Type) t(.ResourceRecords[].Value)n"'
answered Jan 29 '18 at 9:56
SzTibuSzTibu
723
723
add a comment |
add a comment |
To export a hosted zone in AWS Route 53, follow these steps (let say you are using example.com hosted zone):
Step 1: Installation – pip install route53-transfer
Step 2: Backup the zone to a CSV file:
route53-transfer dump example.com backup.csv
Use STDOUT instead of a file
route53-transfer dump example.com –
Step 3: Restore a zone:
route53-transfer load example.com backup.csv
Use - to load from STDIN instead
Migrate between accounts:
Use command line switches for overriding the access and secret keys:
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com
route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
If you are working with private zones, use –private to distinguish private domains:
route53-transfer --private dump example.com example-private.csv
route53-transfer dump example.com example-public.csv
add a comment |
To export a hosted zone in AWS Route 53, follow these steps (let say you are using example.com hosted zone):
Step 1: Installation – pip install route53-transfer
Step 2: Backup the zone to a CSV file:
route53-transfer dump example.com backup.csv
Use STDOUT instead of a file
route53-transfer dump example.com –
Step 3: Restore a zone:
route53-transfer load example.com backup.csv
Use - to load from STDIN instead
Migrate between accounts:
Use command line switches for overriding the access and secret keys:
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com
route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
If you are working with private zones, use –private to distinguish private domains:
route53-transfer --private dump example.com example-private.csv
route53-transfer dump example.com example-public.csv
add a comment |
To export a hosted zone in AWS Route 53, follow these steps (let say you are using example.com hosted zone):
Step 1: Installation – pip install route53-transfer
Step 2: Backup the zone to a CSV file:
route53-transfer dump example.com backup.csv
Use STDOUT instead of a file
route53-transfer dump example.com –
Step 3: Restore a zone:
route53-transfer load example.com backup.csv
Use - to load from STDIN instead
Migrate between accounts:
Use command line switches for overriding the access and secret keys:
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com
route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
If you are working with private zones, use –private to distinguish private domains:
route53-transfer --private dump example.com example-private.csv
route53-transfer dump example.com example-public.csv
To export a hosted zone in AWS Route 53, follow these steps (let say you are using example.com hosted zone):
Step 1: Installation – pip install route53-transfer
Step 2: Backup the zone to a CSV file:
route53-transfer dump example.com backup.csv
Use STDOUT instead of a file
route53-transfer dump example.com –
Step 3: Restore a zone:
route53-transfer load example.com backup.csv
Use - to load from STDIN instead
Migrate between accounts:
Use command line switches for overriding the access and secret keys:
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com
route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
If you are working with private zones, use –private to distinguish private domains:
route53-transfer --private dump example.com example-private.csv
route53-transfer dump example.com example-public.csv
answered Feb 11 '18 at 10:02
Dina KaiserDina Kaiser
1213
1213
add a comment |
add a comment |
You can sign up for Cloudflare.com and add a free website.
Cloudflare will scan your DNS as part of its onboarding.
After import (or maybe during), in "Advanced" below the DNS records, there is an Export DNS file button.
add a comment |
You can sign up for Cloudflare.com and add a free website.
Cloudflare will scan your DNS as part of its onboarding.
After import (or maybe during), in "Advanced" below the DNS records, there is an Export DNS file button.
add a comment |
You can sign up for Cloudflare.com and add a free website.
Cloudflare will scan your DNS as part of its onboarding.
After import (or maybe during), in "Advanced" below the DNS records, there is an Export DNS file button.
You can sign up for Cloudflare.com and add a free website.
Cloudflare will scan your DNS as part of its onboarding.
After import (or maybe during), in "Advanced" below the DNS records, there is an Export DNS file button.
answered Apr 9 at 18:26
Michael ColeMichael Cole
226110
226110
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f535631%2fhow-to-export-a-hosted-zone-in-aws-route-53%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