Hi
I have the same problem. I can use nslookup, host or dig to resolve name.
but I cannot use apt-get to resolve name at the first time. However If I use
nslookup, host, or dig. apt-get can resolve that name. it like a cache on
system.
FYI
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Well, I finally got to the bottom of it.
There seems to be a bug in the DLink G604T router doing DNS under some
circumstances. Even after a firmware upgrade.
I got tcpdump out to look what was happening and saw some very strange things.
For instance, an ftp request to ftp.nl.debian.org was actual
Daniel McBrearty wrote:
Daniel,
First check manual if your router succesfully make a connection to the
internet. I've used those D-link before on belgian internet providers
and sometimes it's hard to get it connected. Especially check the ATM
PVC properties, they differ depending the provid
> Daniel,
>
> First check manual if your router succesfully make a connection to the
> internet. I've used those D-link before on belgian internet providers
> and sometimes it's hard to get it connected. Especially check the ATM
> PVC properties, they differ depending the provider you use.
>
Daniel McBrearty wrote:
search
nameserver 192.168.1.1
Daniel,
First check manual if your router succesfully make a connection to the
internet. I've used those D-link before on belgian internet providers
and sometimes it's hard to get it connected. Especially check the ATM
PVC properti
Daniel McBrearty wrote:
> Adam Aube wrote:
>> This isn't a publicly routable IP address, so it's most likely either the
>> router or the DSL modem acting as a DNS forwarder. This device likely has
>> a web interface - find its status page and see what DNS server it is
>> using.
>>
>> You could al
Daniel McBrearty gmail.com> writes:
>
> changing resolv.conf seems to have no effect. Is it read at start time or each
> time a DNS query happens?
>
> what's curious is that after I change it reverts back to 192.168.1.1 on a
> reboot. I guess this must be in response to something the router is
changing resolv.conf seems to have no effect. Is it read at start time or each
time a DNS query happens?
what's curious is that after I change it reverts back to 192.168.1.1 on a
reboot. I guess this must be in response to something the router is telling it?
--
To UNSUBSCRIBE, email to [EMAIL
> This isn't a publicly routable IP address, so it's most likely either the
> router or the DSL modem acting as a DNS forwarder. This device likely has a
> web interface - find its status page and see what DNS server it is using.
>
> You could also try manually replacing the "192.168.1.1" in /et
Daniel McBrearty wrote:
> antgel wrote:
>> Daniel McBrearty wrote:
>>> When I do apt-get install for a new package (as root ), apt goes to
>>> the ftp server ... and hangs on address 1.0.0.0 (DNS lookup problem?).
>>> I then have to quit, do "ftp ftp.debian.nl.org" (or whatver it is) log
>>> in an
search
nameserver 192.168.1.1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
the default from my ISP. I'm behind a d-link adsl router which is in an
absolutely standard out-of-the-box config, firewall on. The router gets the dns
server automatically I think.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
12 matches
Mail list logo