1. /etc/resolv.conf and DNS --- *must* named be running?
I've got a test PC that I'm going to setup a name server on to host my
company's public web site. I'm going to run the DNS server myself
rather than pay someone else to do it.
I've been having some serious trouble with DNS, nslookup and such.
Some sites can do an nslookup to my domain, some cannot......
I'm installing a new server independant of my main network and
internal DNS
server. This server is a RedHat Linux 7.3 server.
So I'm starting from the very beginning -- no DNS, just testing my
/etc/resolv.conf configuration.
When I point my /etc/resolv.conf file to the ip address of
ns1.savvis.net, I
cannot connect to any machines/web sites/etc that are outside of [what
I
think] is the 'network owned by Savvis'. The reason that I say this
is because of the three web sites that I attempt to connect to I know
that at least two of them have contracts with Savvis (One Net
Communicatins and Symanet, Inc.)
my /etc/resolv.conf file is:
nameserver 209.16.211.42
When I try to connect to a site line Excite.com, I get the following:
%> lynx www.excite.com
Alert!: Unable to access document.
Looking up www.excite.com first
Looking up www.excite.com.com, guessing...
Looking up www.excite.com.edu, guessing...
Looking up www.excite.com.net, guessing...
Looking up www.excite.com.org, guessing...
Can't Access `file://localhost/etc/sysconfig/network-scripts/www.excite.com'
Alert!: Unable to access document.
lynx: Can't access startfile
But if I change my /etc/resolv.conf file to point to a name server not
owned
by Savvis (ns1.one.net), everything works normally. eg:
/etc/resolv.conf:
nameserver 66.83.39.4
%> lynx www.excite.com
[the Excite home page appears normally].
Does Savvis somehow filter this resolution? This hasn't been an issue
before this time because I am running a caching name server on my
gateway to
the Internet. THIS server, however absolutely must not run DNS or a
caching
name server. I'm sure that the admin at One.net wouldn't want me to
use his
name server for my own purposes. It is worth noting that ns2 and
ns3.savvis.net exhibit this behavior as well.
2. mksysb tape problem
3. dhclient.conf to add dns in resolv.conf
4. "ancient" hardware
5. named.conf "option forwarder" vs. resolv.conf "nameserver"?
6. ILOG
7. Looking for sample /etc/named.conf and etc/resolv.conf and /etc/hosts
8. Star Office 5.0
9. DNS: /etc/resolv.conf keeps on growing
10. Q: Simple way to pick up resolv.conf info from DHCP to DNS?
11. Secondary DNS entry in resolv.conf
12. Order of DNS Servers in RESOLV.CONF
13. config /etc/resolv.conf to use /etc/hosts first for DNS??