CoreDNS failed to start cause of "cannot assign requested address" #7564
Description
What happened:
When I started CoreDNS in pod, CoreDNS failed to start the first time but ran normally after a restart. The log reported an error during the first startup:
Listen: listen tcp [fe80::6446:60ff:fe2d:49d9%eth0]:53: bind: cannot assign requested address
What you expected to happen:
CoreDNS started up normally for the first time.
How to reproduce it (as minimally and precisely as possible):
The conditions for replication are still unclear.
Anything else we need to know?:
I use plugin bind in server block, for details, please refer to the corefile.
Environment:
- the version of CoreDNS: v1.12.2
- Corefile:
cluster.local:53 in-addr.arpa:53 ip6.arpa:53 {
bind eth0
errors
health :10053 {
lameduck 5s
}
kubernetes {
pods insecure
fallthrough in-addr.arpa ip6.arpa
ttl 30
endpoint https://10.41.0.1:443
}
log svc.cluster.local "{>id} {remote}:{port} {type} {name} {rcode}" {
class error denial
}
reload
loadbalance
}
- logs, if applicable:
- OS (e.g:
cat /etc/os-release):
linux kernel 5.10.0 - Others:
NIC in pod：
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0@if943: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 66:46:60:2d:49:d9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.18.137.65/32 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::6446:60ff:fe2d:49d9/64 scope link
valid_lft forever preferred_lft forever