Comment 8 for bug 1012860

Revision history for this message
Javier Collado (javier.collado) wrote :

Running the same command, I wasn't able to reproduce the problem.

In may /etc/resolv.conf I see:
nameserver 192.168.122.1 # Added by UTAH

Instead of:
nameserver # Added by UTAH

Let me know if there should be a way to reproduce the problem playing with the network configuration. Otherwise, it looks like this is no longer a problem.