node-dns | Replacement dns module in pure javascript for node.js | Runtime Evironment library
kandi X-RAY | node-dns Summary
kandi X-RAY | node-dns Summary
Replacement dns module in pure javascript for node.js
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- check for benchmarks
- send response to the server
node-dns Key Features
node-dns Examples and Code Snippets
version: "3.8"
services:
frontend:
build: frontend
container_name: clienta-frontend
networks:
default:
aliases:
- clienta.test
backend:
build: backend
Community Discussions
Trending Discussions on node-dns
QUESTION
PROBLEM: For some reason client pod can only resolve fully qualified fully-qualified DNS names including the cluster service suffix.
That problem is stated in this quesion: AKS, WIndows Node, dns does not resolve service until fully qualified name is used
To workaround this issue, I'm using useServiceDnsDomain flag. The documentation (https://strimzi.io/docs/operators/master/using.html#type-GenericKafkaListenerConfiguration-schema-reference ) explains it as
Configures whether the Kubernetes service DNS domain should be used or not. If set to true, the generated addresses with contain the service DNS domain suffix (by default .cluster.local, can be configured using environment variable KUBERNETES_SERVICE_DNS_DOMAIN). Defaults to false.This field can be used only with internal type listener.
Part of my yaml is as follows
...ANSWER
Answered 2020-Oct-30 at 13:30As exmaplained in https://github.com/strimzi/strimzi-kafka-operator/issues/3898, there is a typo in the docs. The right YAML is:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install node-dns
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page