Problem with A record

[Kevin Darcy]

Linux has an /etc/nsswitch.conf or some other system config file that
tells it what nameservers to use, doesn't it? Sounds like your box isn't
configured to use DNS for lookups. nslookup works because it's using
DNS regardless of what the system config says.


- Kevin

aceffa at sogesi.it wrote:

> Hi,
>
> I have a strange problem. I have a linux server(slack 7.1,2.2.13) with
> two eth card one configured on the internal LAN and another on a
> public LAN.
> >From the console if i try to ping to a domain i obtain:
> unknown host www.domain.com.
> But if i try to ask to my dns with nslookup everythings works.
>
> If I set on a workstation on the private LAN the private IP addresse
> of the server the workstation is able to browse.
>
> Sendmail cannot work 'cause it said "Sender domain must resolve".
>
> On the another machine with Slack 7.1, but kernel 2.2.19 everithings
> works. But I don't think kernel should be the problem.
>
> This is my named.conf:
>
> options {
> directory "/igs/dns";
> # listen-on { !localnets; !localhost; any; }; # Non Funziona !!!
> listen-on { !localnets; any; };
> /*
> * If there is a firewall between you and nameservers you want
> * to talk to, you might need to uncomment the query-source
> * directive below. Previous versions of BIND always asked
> * questions using port 53, but BIND 8.1 uses an unprivileged
> * port by default.
> */
> // query-source address * port 53;
> forwarders { 192.106.1.1; };
> };
>
> logging {
> category queries { default_syslog; };
> category cname { null; };
> category lame-servers { null; };
> };
>
> zone "." {
> type hint;
> file "db.root";
> };
>
> zone "0.0.127.in-addr.arpa" {
> type master;
> file "localhost.arpa";
> };
>
> This is my localhost.arpa:
>
> @ IN SOA igs.igs.it. root.igs.it. (
> 1999010100 ;serial
> 86400 ;refresh 8 h.
> 7200 ;retry 2 h.
> 604800 ;expire 7 g.
> 86400 ;minimum 1 g.
> )
>
> IN NS localhost.
> 1 IN PTR localhost.igs.it.
>
> This is my db.root:
>
> A.ROOT-SERVERS.NET. IN A 198.41.0.4
> B.ROOT-SERVERS.NET. IN A 128.9.0.107
> C.ROOT-SERVERS.NET. IN A 192.33.4.12
> D.ROOT-SERVERS.NET. IN A 128.8.10.90
> E.ROOT-SERVERS.NET. IN A 192.203.230.10
> F.ROOT-SERVERS.NET. IN A 39.13.229.241
> G.ROOT-SERVERS.NET. IN A 192.112.36.4
> H.ROOT-SERVERS.NET. IN A 128.63.2.53
> I.ROOT-SERVERS.NET. IN A 192.36.148.17
> L.ROOT-SERVERS.NET. IN A 131.114.192.100
> M.ROOT-SERVERS.NET. IN A 131.154.2.3
> N.ROOT-SERVERS.NET. IN A 192.5.25.5
> O.ROOT-SERVERS.NET. IN A 38.8.50.2
> P.ROOT-SERVERS.NET. IN A 131.175.88.253
>
> Any help would be appraciated.
>
> Thank for your attention
>
> Andrea