Hi All: After upgrading to 4.4 my server(s) will not resolve using the servers listed in resolve.conf. This is not true of a server running a DNS Cache server. I can do a netstat -e and show a connection to the DNS servers but it will not resolve any domain names (please see below). Any thoughts? [root at ftp ~]# dig yahoo.com ; <<>> DiG 9.2.4 <<>> yahoo.com ;; global options: printcmd ;; connection timed out; no servers could be reached [root at ftp ~]# netstat -e Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode tcp 0 0 10.0.2.5:32806 66.81.0.251:domain ESTABLISHED root 17584 Thanks, Ed
A little birdy told me that Ed Morrison said: ] After upgrading to 4.4 my server(s) will not resolve using the servers listed ] in resolve.conf. This is not true of a server running a DNS Cache server. I ] can do a netstat -e and show a connection to the DNS servers but it will not ] resolve any domain names (please see below). Any thoughts? my DNS servers all survived the upgrade fine... with one caveat... the file "/etc/rndc.conf" got updated without any ".rpmnew" preservation taking place... as such, for servers to correctly reload their maps and other such tasks via "rndc" i needed to update that file to re-include the correct information for the key... just figured it deserved a mention... B. Karhan simon at pop.psu.edu PRI/SSRI Unix Administrator
Ed Morrison wrote:> Hi All: > > After upgrading to 4.4 my server(s) will not resolve using the servers > listed in resolve.conf. This is not true of a server running a DNS > Cache server. I can do a netstat -e and show a connection to the DNS > servers but it will not resolve any domain names (please see below). > Any thoughts? > > [root at ftp ~]# dig yahoo.com > > ; <<>> DiG 9.2.4 <<>> yahoo.com > ;; global options: printcmd > ;; connection timed out; no servers could be reachedPlease show your /etc/resolv.conf (and rename it to that, if you really have a /etc/resolve.conf). Ralph -- Ralph Angenendt......ra at br-online.de | .."Text processing has made it possible Bayerischer Rundfunk...80300 M?nchen | ....to right-justify any idea, even one Programmbereich.Bayern 3, Jugend und | .which cannot be justified on any other Multimedia.........Tl:089.5900.16023 | ..........grounds." -- J. Finnegan, USC -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20060905/4964d704/attachment-0002.sig>
Ralph Angenendt wrote:> Ed Morrison wrote: > >> Hi All: >> >> After upgrading to 4.4 my server(s) will not resolve using the servers >> listed in resolve.conf. This is not true of a server running a DNS >> Cache server. I can do a netstat -e and show a connection to the DNS >> servers but it will not resolve any domain names (please see below). >> Any thoughts? >> >> [root at ftp ~]# dig yahoo.com >> >> ; <<>> DiG 9.2.4 <<>> yahoo.com >> ;; global options: printcmd >> ;; connection timed out; no servers could be reached >> > Please show your /etc/resolv.conf (and rename it to that, if you really > have a /etc/resolve.conf). > > Ralph > > ------------------------------------------------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >My /etc/resolv.conf: ; generated by /sbin/dhclient-script search csds.local nameserver 192.168.1.4 nameserver 65.106.1.196 nameserver 65.106.7.196
As it turns out DNS stopped working for my entire network. The problem manifested itself with the 4.4 servers first. The problem was a fat finger error by my ISP. They found the issue and I am working again. Sorry for the false alarm. Ed