Wrong DNS when using DHCP

Hi,

I have installed Mandrake 9.1 in computer connected to D-Link DI-804 that is
connected to an ADSL modem.
When I browse the D-Link I can see that it has retrieved two DNS IPs from my
operator.

The problem is that none of the DHCP clients I've tried (dhclient, dhcpcd
and pump) have been able to retrieve the DNS information correctly.
They all lists the IP of my D-Link (twize!) as DNS.

I have solved the problem by manually editing the resolv.conf and disabeling
the automatic updates of it.

I find it very anoying that I have to do this and wonder if anyone have an
idea about how I could solve this?

"Jens Landgré" <(E-Mail Removed)> wrote in message
news:d3Nmb.35061$(E-Mail Removed)...
> Hi,
>
> I have installed Mandrake 9.1 in computer connected to D-Link DI-804 that
is
> connected to an ADSL modem.
> When I browse the D-Link I can see that it has retrieved two DNS IPs from
my
> operator.
>
> The problem is that none of the DHCP clients I've tried (dhclient, dhcpcd
> and pump) have been able to retrieve the DNS information correctly.
> They all lists the IP of my D-Link (twize!) as DNS.
>


This is the way it's supposed to be. Your router will forward DNS requests
to your ISP's DNS server.


--
Andy Zhang

Remove "removethis" to reply by email

On Sun, 26 Oct 2003 10:09:13 GMT, Jens Landgré <(E-Mail Removed)> wrote:
> I have installed Mandrake 9.1 in computer connected to D-Link DI-804 that is
> connected to an ADSL modem.
> When I browse the D-Link I can see that it has retrieved two DNS IPs from my
> operator.
>
> The problem is that none of the DHCP clients I've tried (dhclient, dhcpcd
> and pump) have been able to retrieve the DNS information correctly.
> They all lists the IP of my D-Link (twize!) as DNS.

Look at it this way. Suppose you turn on your Dlink (or it disconnected
on idle timeout), boot up your PC (or it renews its IP while Dlink is
disconnected), it gets DHCP from Dlink (which has no DNS), the Dlink
connects, but you have no nameservers because you got your DHCP IP before
any internet connection. Then you have to release and renew your IP to
get the nameservers.

Would you rather do that, or simply use the Dlink IP and have it forward
it where it is supposed to go. If that does not make you happy, run your
own DNS (I do, along with forward and reverse zones for my LAN).

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

David Efflandt wrote:

> Would you rather do that, or simply use the Dlink IP and have it forward
> it where it is supposed to go. If that does not make you happy, run your
> own DNS (I do, along with forward and reverse zones for my LAN).

Ok, now I understand how it should work. However it doesn't. I guess my
problem is not where I thought it was.

If I change my resolv.conf to use the Dlink as DNS "dig" gives me the
following response:
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; reply from unexpected source: 10.0.0.2#53, expected 192.168.0.10#53
;; reply from unexpected source: 10.0.0.2#53, expected 192.168.0.10#53

; <<>> DiG 9.2.2 <<>> www.telia.com
;; global options: printcmd
;; connection timed out; no servers could be reached

Why doesn't it accept the source 10.0.0.2?

On Tue, 28 Oct 2003 18:15:48 GMT, Jens Landgré <(E-Mail Removed)> wrote:
> David Efflandt wrote:
>
>> Would you rather do that, or simply use the Dlink IP and have it forward
>> it where it is supposed to go. If that does not make you happy, run your
>> own DNS (I do, along with forward and reverse zones for my LAN).
>
> Ok, now I understand how it should work. However it doesn't. I guess my
> problem is not where I thought it was.
>
> If I change my resolv.conf to use the Dlink as DNS "dig" gives me the
> following response:
> ;; Got SERVFAIL reply from 127.0.0.1, trying next server
> ;; reply from unexpected source: 10.0.0.2#53, expected 192.168.0.10#53
> ;; reply from unexpected source: 10.0.0.2#53, expected 192.168.0.10#53
>
> ; <<>> DiG 9.2.2 <<>> www.telia.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> Why doesn't it accept the source 10.0.0.2?

Why do you have 127.0.0.1 listed as nameserver if not running named?

Apparently your DI-604(?) just relays the DNS and doe not proxy or cache
it properly. Have you checked Dlink web site for a firmware upgrade?
Otherwise see the Dlink hardware forum at http://www.dslreports.com/

You could either put actual nameservers in /etc/resolv.conf and configure
your dhcp NOT to change it, or run your own caching nameserver (likely a
bind or caching nameserver package, but the daemon is called 'named').

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/