Virtual DNS service does not work when the environment has a DNS server

Bug #1311252 reported by Abhishek Chanda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenContrail
Fix Committed
Undecided
Hari Prasad Killi

Bug Description

We have an integrated Contrail + OpenStack environment where the fabric hosts DNS servers (pdnsd). Named fails to startup complaining that it cannot bind. This disables the virtual DNS service in this environment.

Tags: vdns
Changed in opencontrail:
assignee: nobody → Hari Prasad Killi (haripk)
Revision history for this message
Hari Prasad Killi (haripk) wrote :

Please provide the error given by bind. Please check the following:
1) Is named being run from root user.
2) Named is being started with /var/log/named/bind.log as the log file. The /var/log/named directory should exist before it is started.
3) dnsd should be started before named

Revision history for this message
Hari Prasad Killi (haripk) wrote :

Added the option to start DNS on a different port by configuring in the config file.

Changed in opencontrail:
status: New → Fix Committed
Revision history for this message
Hari Prasad Killi (haripk) wrote :
tags: added: vdns
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.