+++ This bug was initially created as a clone of Bug #702112 +++
Description of problem:
I'm using NAT networking for my virtual guests (KVM). In the XML file I have defined the example.com domain and a host which will be assigned static IP address and predefined hostname. The config looks like this:
<bridge name='virbr0' stp='on' delay='0' />
<ip address='192.168.122.1' netmask='255.255.255.0'>
<range start='192.168.122.200' end='192.168.122.254' />
<host mac='52:54:00:bf:ae:e2' name='tester1.example.com' ip='192.168.122.12' />
<bootp file='pxelinux.0' server='192.168.122.11' />
When I create new guest and run the anaconda installer by default it uses DHCP. The result is that IP address is assigned correctly but DNS is not.
Version-Release number of selected component (if applicable):
anaconda in RHEL 6.0 GA
Steps to Reproduce:
1. Cofigure NAT networking using the domain and host tags
2. Assign FQDN for your guest system
3. Install the guest using anaconda with all the default options. Specify the correct MAC address for the network interface.
During stage2 IP address is assigned but /etc/resolv.conf looks like:
no trace of nameserver configuration. All DNS requests fail.
DNS is working.
This happens when I boot the guest using PXE (the guest is part of local beaker lab setup)
If I select to provision RHEL 5.6 from beaker on the same host then /etc/resolv.conf looks like:
In the same environment if I create a new guest with RHEL 6 with a different MAC address it will get a dynamic IP and resolv.conf in stage2 looks like:
(In reply to comment #0)
> In the same environment if I create a new guest with RHEL 6 with a different
> MAC address it will get a dynamic IP and resolv.conf in stage2 looks like:
> domain example.com
> search example.com
> nameserver 192.168.122.1
This is when the guest is created manually using virt-manager and http install source, not PXE boot.
Created attachment 497431 [details]
tarball with logs from stage2 of install with wrong DNS config
Can you please retest with current RHEL 6.1 (I think e.g. Snap 5 should be ok)? /etc/resolv.conf is now managed entirely by NM in anaconda (see bug #687953).
Works for me with RC 4 and it looks like a dup of #687953.
*** This bug has been marked as a duplicate of bug 687953 ***