RSA/DSA Host key generation didn't happen

Did anyone else find that on 5.2-RELEASE, that the RSA and DSA host keys
were not generated on first boot, as happens on other distros? Could this
possibly be related to the DHCP/resolve.conf issue mentioned a while back:

http://makeashorterlink.com/?A5D921F47

I also experienced some strange DHCP problem.

I had configured the machine not to use DHCP on boot for certain reasons not
worth mentioning here. I was going to send a message to a BSD forum asking
about this but I didn't, here is a copy of that message:

>I am no networking expert, and I suspect this is the source of my
>problems.

>I recently installed 5.2R on a machine of mine, and upon attempting to
>setup the network device:

> dhclient rl0
>
> It got assigned an IP from my router correctly; there is a lease in
> /var/db/dhclient.leases, but I am unable to access the internet. I can
ping
> local hosts, but if I try:
>
> ping www.google.com
>
> I get
>
> ping: cannot resolve www.google.com: Host name lookup failure
>
> and this doesn't work with external IPs either
>
> but if I do:
>
> dnsquery -n 192.168.1.1 www.google.com
>
> it returns the correct stuff.
>
> If I do:
>
> netstat -r
>
> the following gets returned:
>

OK, sorry about this, the following is a HTML table as the forum had HTML
support
so you might have to render this under a HTML engine if you are sufficiently
interested in seeing the output:

<table>
<tr><td>Destination</td><td>Gateway</td><td>Flags</td><td>Refs</td><td>Use</
td><td>Netif</td><td>Expire</td> <tr> <td>default</td> <td>192.168.1.1</td>
<td>UGS</td> <td>0</td> <td>0</td> <td>rl0</td> <td></td> </tr> <tr>
<td>localhost</td> <td>localhost</td> <td>UH</td> <td>1</td> <td>112</td>
<td>lo0</td> <td></td> </tr> <tr> <td>192.168.1</td> <td>link#1</td>
<td>UC</td> <td>0</td> <td>0</td> <td>rl0</td> <td></td> </tr> <tr>
<td>192.168.1.1</td> <td>XX:XX:XX:XX:XX:XX</td> <td>UHLW</td> <td>1</td>
<td>4</td> <td>rl0</td> <td>1056</td> </tr> <tr> <td>192.168.1.2</td>
<td>localhost</td> <td>UGHS</td> <td>0</td> <td>0</td> <td>lo0</td>
<td></td> </tr> </table>

> On my 5.1 system, there is a little c by the flags for the router:
>
> UGSc
>
> which corresponds to
>
> RFT_PRCLONING Protocol-specified gnerate new routes on use
>
> so I tried to somehow force this c flag:
>
> route -v change default -cloning
> U: inet 0.0.0.0; inet 0.0.0.0; RTM_CHANGE: Change Metrics or flags: len
112,
> pid: 0, seq 1, errno 0, flags:<UP,GATEWAY,CLONING,STATIC>
> locks: inits:
> sockaddrs: <DST,NETMASK>
>  default default
> change net default
>
> but it doesn't seem to put the little c in the flags list, or change the
> status of the problem.
>
> I'm probably overlooking something simple, but my clue is limited to that
> expressed in this message. So if someone with clue could help me I would
be
> thankful.
>
> Note, that i have no problems setting up network interfaces with the same
> router on another box running 5.1R, it only seems to be this new box with
> 5.2R that is having trouble. Is suspect it has something to do with 5.2R.

OK so this is pretty wierd. I solved this later by putting

problem was wierd but resolved by putting:

nameserver x.x.x.x

in /etc/resolv.conf

I didn't know that just touching it would work like for the other people.

So I don't know, but there seems to be a couple of wierd problems with the
new 5.2R.

Any thoughts?

iooi