DNS not working in Fedora 14
Dick Holland
fedora at xegetix.com
Sat Jan 1 13:59:11 UTC 2011
I've installed F14 on a box that was running F8 (I know, I know...) and
DNS is not working properly.
nslookup and dig can both find google.com quite successfully, but any
other method of trying to connect to remote site (http, telnet, ftp) all
fail with the same error that they cannot resolve the name. I have
disabled SElinux, the firewall, and the iptables and ip6tables services.
Whether I configure the ethernet connection with DHCP or a static IP
address the results are the same, as they are if I'm using 64-bit or
32-bit F14. The results below are for a DHCP setup on 32-bit F14, which
is really straight out of the box.
---------------------------------------------------------------------
Here's /etc/hosts:
192.168.181.122 cobalt.xegetix.com cobalt # Added by NetworkManager
127.0.0.1 localhost.localdomain localhost localhost4
::1 cobalt.xegetix.com cobalt localhost6.localdomain6 localhost6
---------------------------------------------------------------------
Here's /etc/resolv.conf:
# Generated by NetworkManager
domain xegetix.com
search xegetix.com
nameserver 192.168.181.254
nameserver 194.168.4.100
nameserver 194.117.134.19
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 194.168.8.100
---------------------------------------------------------------------
Here's the output from "ifconfig":
eth0 Link encap:Ethernet HWaddr 00:1F:D0:9C:5F:44
inet addr:192.168.181.122 Bcast:192.168.181.255
Mask:255.255.255.0
inet6 addr: fe80::21f:d0ff:fe9c:5f44/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:269 errors:0 dropped:0 overruns:0 frame:0
TX packets:237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39355 (38.4 KiB) TX bytes:37730 (36.8 KiB)
Interrupt:44 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:120 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10144 (9.9 KiB) TX bytes:10144 (9.9 KiB)
---------------------------------------------------------------------
Here's the result of a "ping google.com":
PING google.com (173.194.37.104) 56(84) bytes of data.
64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_req=1
ttl=53 time=16.4 ms
64 bytes from lhr14s02-in-f104.1e100.net (173.194.37.104): icmp_req=2
ttl=53 time=17.1 ms
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 16.476/16.804/17.132/0.328 ms
---------------------------------------------------------------------
Here's the result of an "nslookup google.com":
;; Got recursion not available from 192.168.181.254, trying next server
;; Got recursion not available from 194.168.4.100, trying next server
Server: 194.117.134.19
Address: 194.117.134.19#53
Name: google.com
Address: 173.194.37.104
---------------------------------------------------------------------
Here's the result of a "dig google.com":
; <<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17690
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 271 IN A 173.194.37.104
;; AUTHORITY SECTION:
google.com. 171383 IN NS ns2.google.com.
google.com. 171383 IN NS ns1.google.com.
google.com. 171383 IN NS ns3.google.com.
google.com. 171383 IN NS ns4.google.com.
;; ADDITIONAL SECTION:
ns2.google.com. 171383 IN A 216.239.34.10
ns1.google.com. 171383 IN A 216.239.32.10
ns3.google.com. 171383 IN A 216.239.36.10
ns4.google.com. 171383 IN A 216.239.38.10
;; Query time: 3 msec
;; SERVER: 192.168.181.254#53(192.168.181.254)
;; WHEN: Sat Jan 1 13:10:56 2011
;; MSG SIZE rcvd: 230
---------------------------------------------------------------------
Here's the result of a "telnet google.com 80":
telnet: google.com: Name or service not known
google.com: Host name lookup failure
---------------------------------------------------------------------
I've trawled the forums and mailing list archives and I've searched
Redhat bugzilla. I've seen references to 64-bit DNS problems in F10-F11,
but nothing still open that I can find.
So I've concluded that I'm doing something stupid - or not doing
something sensible and necessary. Can anyone tell me what that might be?
--
Dick Holland
More information about the users
mailing list