From: "Amogh Hooshdar" <amoghhooshdar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 1.0.0.0 DNS replies for many domain names (network)
Date: Fri, 14 Dec 2007 17:20:17 +0530 [thread overview]
Message-ID: <78c462ad0712140350v62ae169fm7a2ce077325ace5f@mail.gmail.com> (raw)
I am having a strange problem with Debian Etch 4.0 (both 64-bit and
32-bit) using 2.6.18 kernel. Most websites do not open with browser,
Pidgin and most other GUI applicatoins. but I am able to ping them
fine. I am also able to do nslookup properly. When I tried to
investigate it with Wireshark net sniffer, I observed the following.
PROBLEM WITH 2.6.18
Say, I try to open www.google.com, browser sends DNS query for
www.google.com to my DNS server which is correctly configured in
resolv.conf. It replies with the correct IP address. www.google.com
redirects the browser to www.google.co.in. browser sends a DNS query
again for www.google.co.in and the DNS server replies with 1.0.0.0
which obviously is the wrong address.
Similar thing happens for many other domains like ftp.us.debian.org,
etc. It is quite random and happens 95% of the times. In other words I
am virtually not able to access internet.
OK WITH 2.6.20
The above was for Debian. With a Ubuntu 7.04 which has 2.6.20 kernel
everything is fine. no problems at all. With windows also no problem
at all.
Is this due to something in the 2.6.18 kernel which is related to the
way it sends a DNS query. Any information on this subject would be
highly appreciated since I am trying to understand why one distro
causes the problem and not the other. is it related to the kernel or
only to the distro?
Key words: DNS, domain, networking, IP address
next reply other threads:[~2007-12-14 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 11:50 Amogh Hooshdar [this message]
2007-12-17 4:51 ` Vaidyanathan Srinivasan
2007-12-17 5:52 ` Amogh Hooshdar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78c462ad0712140350v62ae169fm7a2ce077325ace5f@mail.gmail.com \
--to=amoghhooshdar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®