Re: SuSE 8.0 and slow DNS resolution
From: E Drake (mister__bister_at_hotmail.com)
Date: 07/10/04
- Next message: Agent X: "Re: Windows can't see Apache on Linux machine when in one location, can in other. Linux PC can see server in both locations."
- Previous message: vasanta: "pinging two different URLs, response comes from same IP address (server), Is that possible?"
- In reply to: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Next in thread: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Reply: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 10 Jul 2004 09:59:28 -0700
>
> Jeff, I don't want to piss anyone off, but have you read:
You don't piss me off, since mostly you are right
> man resolv.conf
> man dhcpd
> man hostname
>
> etcetera?
Yes, I have. But apparently not well enough. I also spent quite some
time
looking in news groups, but found mostly advice referring to the
removal
of the search line in resolve.conf, or advice on what order to set the
different DNS addresses in. Both of which did not seem to help me,
because (I suppose) resolv.conf is modified according to what is
received from the router..?
Is it so maybe, that the line with "nameserver router's IP" is added
not as a result of the router response, but based on my DNS settings
(which
I never did anything to actively change until this all started)
>
> I mean, in one of your posts, you state that there would be something wrong
> with the Linux way of working of the DNS...
>
I did not state that, really, did I? I said that manually specifying
the DNS
addresses (which was the advice I found), or removing the search line,
seemed to me to be workarounds. I want the addresses from my ISP to
end
up there... Since, to me that is part of the point with DHCP supplying
this info. So what I said was that I expected there to be another
solution.
ONe I couldn't find
I also wondered, and still wonder, why this works in XP (with the
exact same router settings). I am sure there is a good explanation,
and maybe the defaults in my SuSE setup are simlpy assuming something
else than the XP defaults..? Or maybe I screwed up the defaults.
> Don't.
>
> Make sure that you know what you're talking about before making bold
> statements like that.
Sorry if I upset someone. I was not intending to sound bold. More like
puzzled.
> We've all been in your shoes, and in our own
> respective ways we came out of that position hanving gained knowledge.
>
> You should really read up on domains, domain name solving, etcetera.
> "myhome" indeed indicates something like a M$ default of some kind.
Am I wrong in believing that the search line in resolve.conf comes
into
play only when trying to resolve a partial adress? And, as a
consequence,
that "search myhome" would not do any harm except when such partial
adresses
were used?
I got the above from a book, but now when reading the man pages again,
I am
not so sure...
>
> Somewhere at the install of linux you probably had the opportunity to
> specify your domain name.
That is possible (or likely even), although I must admit I don't
remember...
Alos, it wouldn't affect the router, and hence not the value popping
up
in resolv.conf, would it?
> ou can spcify any name you like there within the
> boundaries set by dns-rules, but in your case it should have been "myhome",
> which is perfectly fine also. After that you should have implemented at
> least one caching DNS to solve your current problem.
Would that solve it? Maybe I am getting things all mixed up here, but
it
seems to me that the main issue is that the router address is first in
the list of nameservers in resolve.conf? And this is happening based
on the router
sending info in the responce to the DHCP request, I beleive? As long
as I allow
dchpcd to modify resolve.conf, this is what happens.
I admit I don't know the details about a caching DNS, but for a
first time ever lookup of an address, wouldn't the problem remain?
I.e.
it cures the symptoms (slow lookups), but does not really solve the
problem?
>
> Another way to work around this (IMHO) is to specify the domain name of
> your provider in the field in your router where it now says "myhome".
Again, I thought the "search myhome" was used only to turn shortened
names into FQDNs? If so, I am not sure I understand how this would
help?
I'll try that however, just to see what happens.
>
> But most importantly: cath up on your reading!
I read and read, and will continue to....just sometimes I get
lost...:-)
And again, it was not my intention at all to upset you. or anyone else
Thanks!
/jeff
- Next message: Agent X: "Re: Windows can't see Apache on Linux machine when in one location, can in other. Linux PC can see server in both locations."
- Previous message: vasanta: "pinging two different URLs, response comes from same IP address (server), Is that possible?"
- In reply to: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Next in thread: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Reply: Gerard Wassink: "Re: SuSE 8.0 and slow DNS resolution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
