antonio montagnani wrote:
2006/2/21, Paul Howarth <paul@xxxxxxxxxxxx <mailto:paul@xxxxxxxxxxxx>>:
On Tue, 2006-02-21 at 09:31 +0100, antonio montagnani wrote:
>
>
> 2006/2/21, Paul Howarth <paul@xxxxxxxxxxxx
<mailto:paul@xxxxxxxxxxxx>>:
> On Mon, 2006-02-20 at 13:42 +0100, antonio montagnani wrote:
> > Please note the difference if I use flag --inet6 (that
> doesn't work)
> > or inet4 that works
> >
> > get -v --inet6-only
> >
>
http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml
> > --13:38:06--
> >
>
http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml
> > => `repomd.xml.6'
> > Risoluzione di download.fedora.redhat.com
<http://download.fedora.redhat.com> in corso...
> fallito: Name or
> > service not known.
> >
> > wget -v --inet4-only
> >
>
http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml
<http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml>
> > --13:40:30--
> >
>
http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml
<http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/repodata/repomd.xml>
> > => `repomd.xml.6'
> > Risoluzione di download.fedora.redhat.com
<http://download.fedora.redhat.com> in corso...
> 66.187.224.20 <http://66.187.224.20>,
> > 209.132.176.20 <http://209.132.176.20>, 209.132.176.220
<http://209.132.176.220>, ...
> > Connessione a
download.fedora.redhat.com|66.187.224.20:80.. .
> connesso.
> > HTTP richiesta inviata, aspetto la risposta... 200 OK
> > Lunghezza: 1,140 ( 1.1K) [text/xml]
> >
> > 100%[====================================>] 1,140
> --.--K/s
> >
> > 13:40:31 (673.08 KB/s) - "repomd.xml.6" salvato [1140/1140]
> >
> >
> > This happens on my router
> > therefore I can't also run yum update
> > yum update
> > Setting up Update Process
> > Setting up repositories
> > Cannot find a valid baseurl for repo: updates-released
> > Error: Cannot find a valid baseurl for repo:
> updates-released
> >
> > Please note that similar commands work on other computer
> behind my
> > router.
> > What shall I investigate???
>
> You might try running your own nameserver on the router and
> see if that
> helps. Or are you doing that already?
>
> Paul.
>
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
>
> Paul,
>
> your suggestion is not clear to me.
> What do you mean by running my own server?
> Now at the moment I am at home, no access to my office router, but I
> can check on this machine what I am doing..if there is any difference
> with the other router that went RH8/RH9/FC1/FC2/FC3/FC4 upgrades!!!!
>
> what I can't understand is why something went broken..
> Another guy on the yum list is reporting a similar problem.
> And, forgive my incompetence, is your sugegstion taking in account
> that other PC conencted to this router work fine??
I'm fumbling around a bit for a solution to be honest. It does appear to
be a name resolution issue though, so running your own nameserver (DNS
server) would be a good start.
You can do it this way:
# yum install caching-nameserver
# chkconfig named on
# service named start
You should then edit /etc/resolv.conf and add the following line above
any other "nameserver" entries:
nameserver 127.0.0.1 <http://127.0.0.1>
See if that helps.
Note: this may have issues if your office LAN uses its own local DNS
domain; you won't be able to resolve names in that domain from the
router. I'm also assuming that your router is statically configured,
i.e. does not use DHCP. If it did, the /etc/resolv.conf file could get
clobbered by the DHCP client.
Paul.
This is my resolv.conf file on the working router and named (BIND) is
not started at boottime
nameserver 62.211.69.150 <http://62.211.69.150>
nameserver 212.48.4.15 <http://212.48.4.15>
and they change at every connection as I get them from my ISP.
What is strange that I can surf the Net, get my e-mails and use synaptic
on the non-working router...it is a kind of magic!!!
OK, try what I suggested last time and if it works, put:
PEERDNS=no
in /etc/sysconfig/network to prevent /etc/resolv.conf getting
overwritten on reboot.
Paul.
