[ale] DNS issues

Dow Hurst dhurst at kennesaw.edu
Mon Jan 14 13:18:44 EST 2002


Kevin,
In your /etc/hosts file you can have your DNS servers listed by IP
matched to hostname pairs, but this isn't usually done.  In the
/etc/resolv.conf you have a "nameserver" entry with the IP of one of
your DNS servers per line, eg.:
nameserver 192.168.0.1
nameserver 192.168.0.2

No other place makes sense on the Linux box.  Check to see if the Name
Service Caching Daemon, nscd, is running.  It normally handles the name
resolution as configured by /etc/resolv.conf and /etc/nsswitch.conf.

On the Windows box you should create a hosts file in your Windows
directory called hosts.dat, if I remember correctly.  In there you could
have the hostname/IP pairs of your local network and possibly your DNS
servers.  The DNS servers are not usually accessed by hostname but only
usually by IP.  Normally in your Windows networking setup you can
specify your nameserver IPs.
Dow


Kevin Stoll wrote:
> 
> I have an interesting problem with DNS on my home network. Set up is Linux
> box acting as router/gateway to internet through a DSL connection with a win
> 98 machine networked. I am using Roaring Penguin/pppoe to connect. On the
> linux machine I have the three DNS servers listed by IP address and then the
> same three by domain name. When I first connect to the internet using the
> Roaring Penguin 'adsl-start' command I can only reach domains from the linux
> machine. It is not until I ping a few IP addresses that the networked
> machine understand how to find web sites and even after that I still have
> trouble reaching some hosts.
> 
> An example would be, I can get to yahoo.com but I can't get to
> resumes.yahoo.com. OR I can get to my own web site if I only type in
> kevinstoll.org but if I try to get to a file it doesn't seem to understand
> how to resolve it. At any rate, what I am trying to say is that sometimes
> the networked machine can resolve a host yet at other times it can not. I
> have not yet determined the pattern by which it does this. The only pattern
> that I have found, although it makes no sense, is that if there is anything
> before or after the root domain, as in www.yahoo.com instead of yahoo.com,
> the networked machine will not resolve but even then there are a few
> instances where that pattern is not true.
> 
> SIGH........
> 
> Thanks for your help in advance.
> 
> Kevin O'Neill Stoll
> http://kevinstoll.org/
> (770) 569-7251
> 
> _________________________________________________________
> 
> Do You Yahoo!?
> 
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
> sent to listmaster at ale dot org.

-- 
__________________________________________________________
Dow Hurst                   Office: 770-499-3428
Systems Support Specialist  Fax:    770-423-6744
1000 Chastain Rd.
Chemistry Department SC428  Email:dhurst at kennesaw.edu
Kennesaw State University         Dow.Hurst at mindspring.com
Kennesaw, GA 30144
*********************************
*Computational Chemistry is fun!*
*********************************

---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.






More information about the Ale mailing list