I have an RH7.2 box running a caching name server that forwards first to my cable ISP's name servers. My resolv.conf contains the following entries:
nameserver 127.0.0.1 nameserver 24.153.23.66 nameserver 24.153.22.67 search ym.phub.net.cable.rogers.com When I log on to updates.redhat.com via ftp or ncftp the following entry appears in /var/log/messages: Mar 24 13:48:50 gw named[23559]: lame server on 'updates.redhat.com.ym.phub.net.cable.rogers.com' (in 'phub.net.cable.rogers.com'?): 24.153.22.14#53 (24.153.22.14 is an authoritative name server for *.ym.phub.net.cable.rogers.com) So it appears that the resolver is adding the search suffix first when fed "updates.redhat.com". The same thing happens if, for example, I access yahoo.com using lynx. I get a log entry that there is a lame server at "yahoo.com.ym.phub.net.cable.rogers.com". I have tried adding the option "ndots:1" to resolv.conf, but it does not prevent the resolver from first searching with the ym.phub.net.cable.rogers.com suffix attached, even though the name searched has one or more dots in it. Is there something broken here? Can anyone suggest a fix? Thanks _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
