Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
4.10.0.0, 4.9.2.0, 4.9.1.0, 4.9.0.1, 4.9.3.0
-
None
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
-
* ACS4.9.0.1 + ACS4.9.1 + ACS4.9.2 + ACS4.9.3 + ACS4.10.0 / CentOS7
* KVM / ACS 4.9.1-4.9.2-4.9.3+4.10.0 / CentOS7
* Isolated networks
Description
Steps to recreate:
- Create VM on isolated network.
- Delete the VM
- Create a new VM with same name.
- Repeat this multiple times.
Result:
- DNS entries are not housekept, allowing for multiples.
- DNSmasq name resolution also returns multiple entries.
- /etc/hosts:
root@r-15-VM:~# cat /etc/hosts ff02::1 ip6-allnodes ff02::2 ip6-allrouters 10.1.1.230 R4VM1 10.1.1.208 R4VM2 ::1 localhost ip6-localhost ip6-loopback 10.1.1.166 R4VM2 10.1.1.1 r-15-VM data-server 10.1.1.24 R4VM2 10.1.1.221 R4VM2 127.0.0.1 localhost r-15-VM
- Name resolving the R4VM2 name:
[root@R4VM1 ~]# nslookup r4vm2 Server: 10.1.1.1 Address: 10.1.1.1#53 Name: r4vm2.cs2cloud.internal Address: 10.1.1.221 Name: r4vm2.cs2cloud.internal Address: 10.1.1.208 Name: r4vm2.cs2cloud.internal Address: 10.1.1.166 Name: r4vm2.cs2cloud.internal Address: 10.1.1.24
Attachments
Issue Links
- links to