Can anyone explain the following behavior to me? [jgreen at t-rex ~]$ nslookup proteome.hpcc.triad.local Server: 127.0.0.1 Address: 127.0.0.1#53 Name: proteome.hpcc.triad.local Address: 10.2.149.1 [jgreen at t-rex ~]$ nslookup proteome.vlan88.hpcc.triad.local Server: 127.0.0.1 Address: 127.0.0.1#53 Name: proteome.vlan88.hpcc.triad.local Address: 192.168.88.179 [jgreen at t-rex ~]$ nslookup proteome Server: 127.0.0.1 Address: 127.0.0.1#53 Name: proteome.hpcc.triad.local Address: 10.2.149.1 [jgreen at t-rex ~]$ nslookup proteome.vlan88 Server: 127.0.0.1 Address: 127.0.0.1#53 ** server can't find proteome.vlan88: SERVFAIL My /etc/resolv.conf is: [jgreen at t-rex ~]$ cat /etc/resolv.conf search hpcc.triad.local nameserver 127.0.0.1 I don't understand why it's not using the search field from /etc/resolv.conf for the second short name (proteome.vlan88). Any idea what can I do to get this working? Thanks, --Joe
Joe Greenseid wrote on Fri, 18 Jan 2008 17:57:39 -0500:> I don't understand why it's not using the search field from > /etc/resolv.conf for the second short name (proteome.vlan88). Any > idea what can I do to get this working?1. nslookup is deprecated, use host 2. it interprets any hostname with a dot in it like an FQDN, e.g. it transforms abc.def -> abc.def. Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
On Friday 18 January 2008 17:57, Joe Greenseid wrote:> Can anyone explain the following behavior to me?What does your resolve.conf and hosts look like? -- Regards Robert Smile... it increases your face value! Linux User #296285 http://counter.li.org
On 1/18/08, Joe Greenseid <jgreen at thunderlizards.net> wrote:> Can anyone explain the following behavior to me? >/snip from the DNS and BIND bible :-) talking about the "options" statement in resolve.conf The second setting you can modify is ndots, which sets the minimum number of dots a domain name argument must have for the resolver to look it up beforeapplying the search list. By default, one or more dots will do; this is equivalent to ndots:1. The resolver first tries the domain name as typed as long as the name has any dots in it. You can raise the threshold if you believe your users are more likely to type partial domain names that will need the search list applied. For example, if your local domain name is mit.edu and your users are accustomed to typing: % ftp prep.ai and having mit.edu automatically appended to produce prep.ai.mit.edu, you may want to raise ndots to two so that your users won't unwittingly cause lookups to the root name servers for names in the top-level ai domain. You could do this with: options ndots:2 this would mean that in order to use FQDNs then you would need to use a trailing "." to specify them which can upset some clients. hth mike