Re: resolver problem

From: Dances With Crows (danceswithcrows_at_usa.net)
Date: 07/15/03 

Date: 15 Jul 2003 00:40:24 GMT

On Tue, 15 Jul 2003 00:16:27 GMT, Michael Lodman staggered into the
Black Sun and said:
> Platform: Intel xscale BE
> OS: MV 2.4.17

MV? This a distro, or what? If this isn't a Linux distro of some sort,
you're in the wrong newsgroup. This message assumes Linux behavior,
other OSes may vary, "man resolv.conf" for the complete story.

> I can't seem to get the resolver working. I have a resolv.conf file,
> but the system will never translate a name for me. I can ping
> addresses directly on the internet, just not by name.

/etc/resolv.conf 's format is quite simple:

search example.org
nameserver 1.2.3.4
nameserver 5.6.7.8

The "search" line is optional but recommended. You set this to the
domain name of wherever you are, and if you try to resolve "machine",
the resolver appends "example.org" and then tries to resolve
"machine.example.org".

There must be at least one "nameserver" line, and it must contain the IP
address of a valid Domain Name Server. If there are 2 nameserver lines,
the first one is used as the primary DNS, and the second one gets
queried if the first one doesn't respond. If you don't know the IP of
your DNS machine, talk to your sysadmin and find out. If your device
gets its IP via DHCP, the DHCP server should fill in the DNS entries
automatically.

You can use "host -v somewhere.org" to get a better look at what the
name resolver is doing. HTH, 

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / 
http://www.brainbench.com     /  "He is a rhythmic movement of the
-----------------------------/    penguins, is Tux." --MegaHAL

Relevant Pages

  • Re: host/domain dns resolution conflict
    ... I have a linux ... > which is registered publicly to resolve to say 10.1.1.100. ... > addresses of my dns servers. ... > Do I need to rename my domain? ...
    (microsoft.public.win2000.dns)
  • Re: bind problem
    ... > would leave you with only one delegated nameserver, ... I would suggest instead that you moved your DNS hosting ... PDNS and SDNS for all the domains we are hosting. ... resolve any domains which is binded to it. ...
    (Fedora)
  • Re: Reasons for not resolving
    ... Why would you use Google to determine whether a web site is up or not? ... It's not even clear to me that you're having a DNS problem. ... Once you've determined that you can't resolve a particular name, then something you might try is a "dig +trace" on the name, from your nameserver. ... It will not, however, exactly match what your nameserver is doing unless you have a completely "vanilla", iterative-resolving configuration. ...
    (comp.protocols.dns.bind)
  • Re: bind problem
    ... >> nameserver, which is not a great idea anyway from a reliability point ... >> you moved your DNS hosting elsewhere, ... > able to resolve any domains which is binded to it. ...
    (Fedora)
  • Re: resolver problem
    ... If this isn't a Linux distro of some sort, ... nameserver 1.2.3.4 ... domain name of wherever you are, and if you try to resolve "machine", ... your DNS machine, talk to your sysadmin and find out. ...
    (comp.os.linux.networking)
Loading