Amazon web services kops更新群集失败,原因是“DNS查找NS记录时出错”`没有这样的主机` 环境 我想做什么
我想在我的域Amazon web services kops更新群集失败,原因是“DNS查找NS记录时出错”`没有这样的主机` 环境 我想做什么,amazon-web-services,kubernetes,kops,Amazon Web Services,Kubernetes,Kops,我想在我的域xway.me上创建一个Kubernetes集群 我找到并尝试了 我创建了一个集群并试图将terraform文件打印为输出,但失败了 $ kops version Version 1.18.2 (git-84495481e4) Kubernetes Cluster Version: 1.18.10 我试过的 我添加了--dns private 但是我得到了未知标志--dns 现在我的resolv.conf在这里 $ kops update cluster \ --out=
xway.me
上创建一个Kubernetes集群
我找到并尝试了
我创建了一个集群并试图将terraform文件打印为输出,但失败了
$ kops version
Version 1.18.2 (git-84495481e4)
Kubernetes Cluster Version: 1.18.10
我试过的
我添加了--dns private
但是我得到了未知标志--dns
现在我的resolv.conf在这里
$ kops update cluster \
--out=. \
--target=terraform \
--state s3://xway.me-kops \
--name xway.me
error doing DNS lookup for NS records for "xway.me": lookup xway.me on 127.0.0.53:53: no such host
我将此代码添加到/etc/resolv.conf中
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
search ad.oit.ac.jp
然后我犯了这个错误
search xway.me
添加nameserver 8.8.8.8
也失败
error doing DNS lookup for NS records for "xway.me": lookup xway.me on 127.0.0.53:53: server misbehaving
使用KOP创建:
error doing DNS lookup for NS records for "xway.me": lookup xway.me on 127.0.0.53:53: no such host
我想知道
我如何才能成功运行
kops update cluster
?当您使用私有DNS记录时,它们通常不会在本地解析。您需要在启用了专用路由53记录的VPC中托管DNS forwareder
kOps记录不会公开任何特别敏感的内容,但是如果您不想使用公共记录,可以选择使用
不过还是有一个原因的
$ kops create cluster --name xway.me --state s3://xway.me-kops
cluster "xway.me" already exists; use 'kops update cluster' to apply changes