Kops: Confusion with the AWS Route53 readme

Created on 27 Jul 2017  路  3Comments  路  Source: kubernetes/kops

Hi,

I'm having a few problems trying to get started with Kops, using a domain I bought via AWS. I have no hosted zones setup, I followed the instructions from here.

There's some confusion on my part with what a subdomain is. This is what I tried:

  • All the preliminaries: S3 bucket, CLI tools, AWS configure, IAM user/group/role
  • Create new hosted zone: example.com
  • Copy the NS servers from AWS domains into its NS records. e.g.:
ns-592.awsdns-10.net
ns-1694.awsdns-19.co.uk
ns-1235.awsdns-26.org
ns-454.awsdns-56.com
  • Run kops create cluster --name=test.example.com --cloud=aws --zones=eu-west-1a --state=s3://mybucket

I get the error returned:

error doing DNS lookup for NS records for "example.com": lookup example.com on [fec0:0:0:ffff::2]:53: dial udp [fec0:0:0:ffff::2]:53: connect: invalid argument

I've tried variations the guide suggests: creating a subdomain NS record and copying the domain NS records there, and creating a hosted zone for subdomain.example.com

This is Bash on Ubuntu for Windows - could this be the problem?

aredocumentation

Most helpful comment

I have same issue Doing DNS lookup to verify NS records for "k8s-tf.**-poc.com" . no such host
Can you please explain the NS record changes you did to make this host visible ???

this was from setting the nameservers incorrectly in the zone. Once I'd done this everything was fine.

All 3 comments

kops create cluster --name=test.example.com --cloud=aws --zones=eu-west-1a --state=s3://mybucket

test.example.com needs to be your domain We need to be more clear that example.com is your domain. We probably want to use a env variable through the examples and explain to set the environment variable to your cluster name with a domain.

Embarassingly, this was from setting the nameservers incorrectly in the zone. Once I'd done this everything was fine.

Some feedback on the docs - it would help if there was a pre-requisites section before running any kops commands.

I also switched to Gossip and everything worked flawlessly.

I have same issue Doing DNS lookup to verify NS records for "k8s-tf.**-poc.com" . no such host
Can you please explain the NS record changes you did to make this host visible ???

this was from setting the nameservers incorrectly in the zone. Once I'd done this everything was fine.

Was this page helpful?
0 / 5 - 0 ratings