On Mon, 30 Aug 2004 15:32:40 -0400, Allen Winter <winterz@xxxxxxxxxxx> wrote: > Hi, > > A few months ago I posted the enclosed message and was given the fix to turn off ipv6 support, > which has worked fine for me ever since (i.e, add the line 'install ipv6 /bin/true' to /etc/modprobe.conf) > > Recently the DNS problems I described have come back... I did upgrade a new kernel using yum. > I still see the ipv6 line in my /etc/modprobe.conf file so I am at a loss. Any ideas as to what may > be causing resolver "dropouts"?? > > Regards and Help! > Allen > ------------------- > > Subject: Need help with a DNS problem > Date: Friday 04 June 2004 01:04 pm > From: Allen Winter <winterz@xxxxxxxxxxx> > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > > Howdy, > > I am having a strange issue on my new Fedora Core 2 install with DNS. > > I have three systems connected to ADSL via a Netgear WGR214v2 Router, > with one running Redhat 9, one running FC1, and the other my new FC2 system. > > The Redhat system is running dhcpcd and has no problem getting addresses. > The FC1 system is running dhclient and had no problem getting addresses. > > The new FC2 system is also running dhclient and fails to get addresses for only > a *few* names I've encountered so far. And dig will give me an answer for those > names, but nslookup will fail. I have looked up everything I know and compared > the FC1 and FC2 systems and they look to be configured the same. > > For example, > % dig myfidelity.members.fidelity.com > > ; <<>> DiG 9.2.3 <<>> myfidelity.members.fidelity.com > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3837 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;myfidelity.members.fidelity.com. IN A > > ;; ANSWER SECTION: > myfidelity.members.fidelity.com. 6056 IN CNAME myfidelity.members.retail.fidelity.com. > > ;; AUTHORITY SECTION: > retail.fidelity.com. 52 IN SOA dns3dccfw01.fidelity.com. hostmaster.retail.fidelity.com. 2004060332 10800 3600 604800 60 > > ;; Query time: 25 msec > ;; SERVER: 192.168.0.1#53(192.168.0.1) > ;; WHEN: Fri Jun 4 13:01:26 2004 > ;; MSG SIZE rcvd: 148 > > % nslookup myfidelity.members.fidelity.com > Server: 192.168.0.1 > Address: 192.168.0.1#53 > > ** server can't find myfidelity.members.fidelity.com: NXDOMAIN > > Oh, and I forgot to mention that every now and then nslookup will return an address for myfidelity.members.fidelity.com, > but that is not the typical case. > > Any ideas? > Regards, > Allen Hi Allen, There may be an incompatibility with the DNS proxy in your router, or your ISP's DNS server. Your message states that "dig will give me an answer ..." but your example shows dig failing: the status is NXDOMAIN, and the IP address does not appear anywhere in the output. Dig from here shows: ; <<>> DiG 9.2.2 <<>> myfidelity.members.fidelity.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45422 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;myfidelity.members.fidelity.com. IN A ;; ANSWER SECTION: myfidelity.members.fidelity.com. 85708 IN CNAME myfidelity.members.retail.fidelity.com. myfidelity.members.retail.fidelity.com. 60 IN A 155.199.8.119 ;; AUTHORITY SECTION: retail.fidelity.com. 208 IN NS dns3mk2fw01.fidelity.com. retail.fidelity.com. 208 IN NS dns3mr4fw01.fidelity.com. retail.fidelity.com. 208 IN NS dns3dccfw01.fidelity.com. ;; Query time: 9 msec ;; SERVER: 69.56.188.210#53(69.56.188.210) ;; WHEN: Mon Aug 30 17:58:20 2004 ;; MSG SIZE rcvd: 183 Try dig @69.56.188.210 myfidelity.members.fidelity.com If that also fails, the trouble is probably with your FC2; you could use ethereal to see how the query or response is being corrupted. If it works, try dig @<your.isp's.nameserver> myfidelity.members.fidelity.com If that succeeds, the problem is probably in your router; specifying explicit nameservers in FC2 should be a workaround. If it fails, your ISP's server may be overly fussy; try using other DNS servers near you (that accept outside queries). --Stewart
