Description of problem:
i set up a f13 guest this morning and the network was acting strangely. after a long while i came up with the attached snapshot.
note that /etc/resolv.conf has the ip 192.168.122.1 as my nameserver
also must say that i would be able to resolve for like a minute then it wouldnt for something like 5 to 10 minutes (i think depending on the dhcp lease) this behaviour was cyclic.
tested in kde and gnome.
i had a pretty long stretch of time where it was resolving pretty good.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 416804 [details]
f13 network manager shows dns ip is reversed
ummm... i did a yum groupinstall on virtualisation of the f13 guest if thats any help.
but that still doesnt explain why the ip is being reversed
I don't think this is virt-manager or libvirt related. Re-assigning to NetworkManager for triaging.
What's the output of rpm -qa | grep NetworkManager inside the VM?
The reversed addresses issue is just displaying bug in kdenetworkmanager applet; corrected 4 weeks ago, BTW:
So I think the bug should be closed. If you have another issue, please describe in more detail and please include /var/log/messages.