On Tue, Feb 9, 2010 at 7:16 PM, Tim <ignored_mailbox@xxxxxxxxxxxx> wrote: > > Wild guess: Look at your resolv.conf files. It is very simple (I think): ; generated by /sbin/dhclient-script search bom.gov.au nameserver 134.178.14.1 nameserver 134.178.14.3 > But, with the amount of blanking out of details in your reports, they're > next to useless for anyone to diagnose anything with. Have a look at > your message headers, if you see the same addresses as you've been > hiding, then there's no point hiding them. Post your error reports with > the real addresses showing. > The full dig messages (querying windows server followed by unix server): ==== [timl@timl ~]$ dig www.bom.gov.au ; <<>> DiG 9.6.1-P3-RedHat-9.6.1-16.P3.fc12 <<>> www.bom.gov.au ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15815 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.bom.gov.au. IN A ;; ANSWER SECTION: www.bom.gov.au. 14 IN A 210.8.42.125 ;; Query time: 0 msec ;; SERVER: 134.178.14.1#53(134.178.14.1) ;; WHEN: Wed Feb 10 09:47:54 2010 ;; MSG SIZE rcvd: 48 [timl@timl ~]$ dig @134.178.6.5 www.bom.gov.au ; <<>> DiG 9.6.1-P3-RedHat-9.6.1-16.P3.fc12 <<>> @134.178.6.5 www.bom.gov.au ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33002 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;www.bom.gov.au. IN A ;; ANSWER SECTION: www.bom.gov.au. 13 IN A 210.8.42.125 ;; AUTHORITY SECTION: www.bom.gov.au. 600 IN NS bom-aapt-scss.bom.gov.au. www.bom.gov.au. 600 IN NS bom-aapt-pcss.bom.gov.au. ;; ADDITIONAL SECTION: bom-aapt-pcss.bom.gov.au. 600 IN A 210.8.186.42 bom-aapt-scss.bom.gov.au. 600 IN A 210.8.42.106 ;; Query time: 1 msec ;; SERVER: 134.178.6.5#53(134.178.6.5) ;; WHEN: Wed Feb 10 09:48:47 2010 ;; MSG SIZE rcvd: 136 === >> work around that has been found is to run dnsmasq on the Fedora >> workstations. > > Isn't that the kludge suggested for IPv6 problems? (I can't remember.) > If so, look into either getting IPv6 working properly, or *completely* > disabled. I have heard that dnsmasq has been used as work around bad DNS resolvers inside ADSL modems that don't handle queries for AAAA records properly. The workstations in question don't seem to have this issue. IPv6 is enabled but there are no v6 gateways/routers on the network so they only have link-local addresses. Tim. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
