From: Andreas (andreajaifi.uio.no)
Date: Tue Apr 01 2003 - 13:45:38 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello and thanks for the replies,

At 03:31 11.04.2005 +1000, you wrote:
>One thing to note, you need to insert your DNS addresses into the file
>/etc/resolv.conf file, here is an example:
>
># cat /etc/resolv.conf
>search nsw.optushome.com.au
>nameserver 1.1.1.1
>nameserver 2.2.2.2
>
>If you find a way to make DHCP automatically update this file, let me
>know,
>
>Thx :-D
>Cheers
This was already set in dhclient.conf. I also added another nameserver just
in case. Anyway, it wasn't that, lynx to google's IP gave this:

$ lynx 216.239.53.99

Looking up 216.239.53.99 first.
Looking up 216.239.53.99.
Making HTTP connection to 216.239.53.99.
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://216.239.53.99/

Of course, I went for a nap, woke up 8 hours later and it now works, both
dns and normal connectivity.

>Yup. That happened to me to. I could reinstall
>Linux -- any version -- and FeeBSD and I'd always
>have 68.69.67.110 as my IP. One install of
>OpenBSD changed my IP. IP hasn't changed since
>(even when I reinstalled OpenBSD). Wonder why.
>
>-Dan
It seems to be retrieving a new IP every time it renews the dhcp lease, not
just at first install.

So it works now, but I still don't know what the problem is. Could it have
something to do with the default settings in dhclient.conf? And does
sending -HUP to dhclient renew it? I ask this because resolv.conf was
updated some time during my nap (the dns server I manually added was
removed during this time). Perhaps that could be an ad-hoc way of solving
the problem?

Thanks again,
Andreas Jacobsen

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]