DNS Service shows as down after configuration on the NSX V Edge
search cancel

DNS Service shows as down after configuration on the NSX V Edge

book

Article ID: 336477

calendar_today

Updated On:

Products

VMware NSX Data Center for vSphere VMware NSX for vSphere

Issue/Introduction

IP Address configured internal interface is required to enable DNS service on the NSX V Edge.

Symptoms:
After configuring DNS service on the NSX V Edge,

  • DNS service shows as "Down".

  • When you run show log follow command on edge console, you see entries similar to:
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: CONFIG_MGR :: --------------- Pre-configuring each configurators ---------------
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: CONFIG_MGR :: config dns...
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: C_DNS :: Executing DNS feature configuration...
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: C_DNS :: No DNS configuration. Stopping DNS.
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.debug] DEBUG :: C_ServiceControl :: GetServerStatus: dns is DOWN
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.debug] DEBUG :: C_DNS :: DNS is already DOWN, do nothing
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: CONFIG_MGR :: --------------- Applying the configuration ---------------
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.info] INFO :: CONFIG_MGR :: update dns...
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.debug] DEBUG :: C_ServiceControl :: GetServerStatus: dns is DOWN
2016-05-05T14:55:09+00:00 <ESG-ID>-0 config: [daemon.debug] DEBUG :: C_ServiceControl :: GetServerStatus: dns is DOWN
  • When you run show manager log on NSX Manager console, you see entries similar to:
2016-05-09 08:51:17.192 GMT INFO TaskFrameworkExecutor-2 DnsVsePojoConverterBase:11 - Disable DNS service as there is no DNS listener defined. This could either because no Edge vNic be defined, or user defined empty listener in DNS configuration.
2016-05-09 08:51:17.205 GMT INFO TaskFrameworkExecutor-2 DnsVsePojoConverterBase:11 - Disable DNS service as there is no DNS listener defined. This could either because no Edge vNic be defined, or user defined empty listener in DNS configuration.
2016-05-09 08:51:17.221 GMT INFO TaskFrameworkExecutor-2 DnsVsePojoConverterBase:11 - Disable DNS service as there is no DNS listener defined. This could either because no Edge vNic be defined, or user defined empty listener in DNS configuration.
 
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
 
 



Environment

VMware NSX for vSphere

Cause

When DNS Service is enabled, it will try to bind with internal type of interface configured IP address. It fails when this interface type doesn't exist on the NSX edge.

 
Note: This generally occurs on NSX edges which are configured as a load balancers with only external type interface configured.

Resolution

To resolve this issue, configure an internal interface with IP Address on the NSX V edge to allow DNS to be used.

Powered by Wolken Software