felipe1982 wrote:
>
> Code:
> --------------------
> smoothwall (root) ~ $ cat /etc/hosts/
> 127.0.0.1 localhost
> 192.168.0.1 smoothwall smoothwall.local
> 192.168.0.69 anarchy anarchy.local
> --------------------
> ‘anarchy’ and ‘anarchy.local’ are defined in the smoothwall hosts file.
> In smoothwall, I added “DNS suffix” as “local” and windows box (another
> PC on my network) miraculously plays well with this new addition. I used
> to have to type “anarchy.” with the dot to get it to work (on both SUSE
> and Windows) but I hated having to type “ftp://anarchy.:28” The dot &
> colon looked so ugly, and awkward to type. After adding “DNS Suffix
> local” wow the windows machine can ping ‘anarchy’ (no dot) and connect
> to FTP (no dot).
>
> “local” suffix works in SUSE, too, by having -ONLY-“nameserver”
> declaration in /etc/resolv.conf. “search local” and “domain local” fail
> to resolve with ping and fail in Konqueror (ftp and sftp and fish and
> ssh), but resolve 100% fine with ‘nslookup’ ‘dig’ ‘ssh’ ‘ftp’ in a
> console.
> Code:
> --------------------
> felipe@suse-amd:~> cat /etc/resolv.conf
> #
> #/etc/resolv.conf
> #search declaration enabled
> search local
> nameserver 192.168.0.1
> felipe@suse-amd:~> dig anarchy
>
> ; <<>> DiG 9.4.2 <<>> anarchy
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61734
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;anarchy. IN A
>
> ;; ANSWER SECTION:
> anarchy. 0 IN A 192.168.0.69
>
> ;; Query time: 14 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Thu Jul 10 23:40:44 2008
> ;; MSG SIZE rcvd: 41
>
> felipe@suse-amd:~> dig anarchy.local
>
> ; <<>> DiG 9.4.2 <<>> anarchy.local
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62445
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;anarchy.local. IN A
>
> ;; ANSWER SECTION:
> anarchy.local. 0 IN A 192.168.0.69
>
> ;; Query time: 1 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Thu Jul 10 23:40:46 2008
> ;; MSG SIZE rcvd: 47
> felipe@suse-amd:~> ping anarchy.local
> ping: unknown host anarchy.local
> felipe@suse-amd:~> ping anarchy
> ping: unknown host anarchy
> felipe@suse-amd:~>
> --------------------
>
> Code:
> --------------------
> felipe@suse-amd:~> cat /etc/resolv.conf ; dig anarchy ; dig
> anarchy.local ; ping -c 2 anarchy ; ping -c 2 anarchy.local
> #
> #/etc/resolv.conf
> #search declaration DISABLED
> #search local
> nameserver 192.168.0.1
>
> ; <<>> DiG 9.4.2 <<>> anarchy
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8643
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;anarchy. IN A
>
> ;; ANSWER SECTION:
> anarchy. 0 IN A 192.168.0.69
>
> ;; Query time: 1 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Thu Jul 10 23:43:44 2008
> ;; MSG SIZE rcvd: 41
>
>
> ; <<>> DiG 9.4.2 <<>> anarchy.local
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56985
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;anarchy.local. IN A
>
> ;; ANSWER SECTION:
> anarchy.local. 0 IN A 192.168.0.69
>
> ;; Query time: 1 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Thu Jul 10 23:43:44 2008
> ;; MSG SIZE rcvd: 47
>
> PING anarchy (192.168.0.69) 56(84) bytes of data.
> 64 bytes from anarchy (192.168.0.69): icmp_seq=1 ttl=64 time=4.77 ms
> 64 bytes from anarchy (192.168.0.69): icmp_seq=2 ttl=64 time=0.118 ms
>
> — anarchy ping statistics —
> 2 packets transmitted, 2 received, 0% packet loss, time 1003ms
> rtt min/avg/max/mdev = 0.118/2.444/4.771/2.327 ms
> ping: unknown host anarchy.local
> felipe@suse-amd:~>
> --------------------
>
>
Hmmm, strange.
I know this isn’t the best answer, but since you’re using static IP’s, why not
put
192.168.0.69 anarchy.local anarchy
into suse-amd’s /etc/hosts file?
Yes, this is not supposed to be needed when using an upstream domain server.
Are you possibly using some sort of proxy on suse-amd? making it parse ‘x’
and ‘x.local’ differently?
Unrelated question: Why have ftp on port 28? Just wondering.
Loni
L R Nix
lornix@lornix.com