vDNS Debugging

Steps to debug virtual-DNS issues

If there is a specific host/VM not getting resolved,

• Find hypervisor on which requesting VM is running (via nova show or alternate)
• Access http://hypervisor-ip:8085/Snh_SandeshTraceRequest?x=DnsBind to get how vrouter-agent handled request for dns resolution
• Find hypervisor on which VM whose name is not resolving
• Access http://hypervisor-ip:8085/Snh_SandeshTraceRequest?x=XmppMessageTrace to see if vrouter-agent sent the VM details to the contrail-dns service, for example (gist):

2016-02-25 17:14:57.079 XmppTxStream: Sent xmpp message to: 100.96.96.209 Port 8093 Size: 452 Packet: <?xml version="1.0"?> <iq type="set" from="<HYPERVISOR>/dns" to="network-dns@contrailsystems.com/dns-peer" id="10020"> <dns transid="10020"> <update> <virtual-dns>default-domain:project-name-virtual-DNS</virtual-dns> <zone>project- name.local</zone> <entry> <class>1</class> <type>1</type> <name>vm-hostname</name> <data>10.20.22.5</data> <ttl>86400</ttl> <priority>0</priority> </entry> </update> </dns> </iq> $ controller/src/xmpp/xmpp_connection.cc 211

• Access http://controller-ip:8092/Snh_SandeshTraceRequest?x=XmppMessageTrace to see if contrail-dns received message from vrouter-agent about VM presence
• Access http://controller-ip:8092/Snh_SandeshTraceRequest?x=DnsBind to see whether contrail-dns programmed bind entries correctly on every controller
• Access http://controller-ip:8092/Snh_ShowDnsConfig to see which records the controller is aware of for this virtual dns. The last column, installed, must be true which indicates the record was successfuly sent to bind/named
• grep in /etc/contrail/dns/* in every controller to check presence of entry. zone files are lazily created and thus do not indicate a problem if grep does not find anything. The opposite is true for jnl files, a positive match on the jnl file also does not indicate a that named is aware of such records.s