[ https://issues.apache.org/jira/browse/CLOUDSTACK-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Zhou closed CLOUDSTACK-512. ------------------------------- > remove hostname in a virtual router's DNS service, after expunging VM > --------------------------------------------------------------------- > > Key: CLOUDSTACK-512 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-512 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller > Affects Versions: pre-4.0.0 > Reporter: Choonho Son > Assignee: Wei Zhou > > The domain name of guest VM is not deleted, even though the guest VM is > expunged. > Scenario: > 1. Deploy VirtualMachine with hostname "head1" > 2. Delete "head1" VirtualMachine > 3. Deploy VirtualMachine with hostname "head1" > 4. Delete "head1" VirtualMachine > ... > After repeating this process, ask ip address of "head1" > nslookup head1 > The result looks like > [root@repo src-conf]# nslookup head1 > Server: 172.27.0.1 > Address: 172.27.0.1#53 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.114.224 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.110.235 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.182.109 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.76.251 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.196.212 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.116.53 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.35.214 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.248.170 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.33.158 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.116.64 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.71.218 > Name: head1.cs82epc-dev.ucloud.com > Address: 172.27.65.181 > Problem: > - Other guest VM cannot connect "head1" VM using domain name, > - Because only one IP address is valid. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira