Summary: DNS problem on Solaris 9

From: Andreas Höschler (ahoesch_at_smartsoft.de)
Date: 09/24/04

  • Next message: Rich Bonfoey: "JNI FC1-1063 and LSI SANS"
    Date: Fri, 24 Sep 2004 21:40:51 +0200
    To: sunmanagers@sunmanagers.org
    
    

    Hello,

    I rechecked the config for the 10th time and finally discovered a
    difference between my working server and the one I have here. I had
    <zone "0.1.168.192.in-addr.arpa" > in /etc/named.conf. This seems to
    have been the show-stopper. I finally managed to get it working. Here
    are the relevant pieces.

    $TTL 3h
    1.168.192.in-addr.arpa. IN SOA smartsoft-hl.de.
    root.smartsoft-hl.de. (
                                     2004092410 ; Serial
                                     86400 ; Refresh
                                     7200 ; Retry
                                     604800 ; Expire
                                     86400 ; Minimum
    )

    1.168.192.in-addr.arpa. IN NS smartsoft-hl.de.
    1 IN PTR merkur.smartsoft-hl.de.

    **************************************************************

    zone "1.168.192.in-addr.arpa"
    {
             type master;
             file "smartsoft-hl.de.rev";
    };

    Thanks to all!

    Regards,

       Andreas

    > I am back at my Solaris 9 server and still had no luck getting DNS to
    > work. I have a very similary configured Solaris 8 box that works. If I
    > execute "nslookup -d2" there I get
    >
    > ***********************************************************************
    > ************
    > bash-2.05# nslookup -d2
    > ;; res_nmkquery(QUERY, 1.1.168.192.in-addr.arpa, IN, PTR)
    > ------------
    > SendRequest(), len 42
    > HEADER:
    > opcode = QUERY, id = 43558, rcode = NOERROR
    > header flags: query, want recursion
    > questions = 1, answers = 0, authority records = 0,
    > additional = 0
    >
    > QUESTIONS:
    > 1.1.168.192.in-addr.arpa, type = PTR, class = IN
    >
    > ------------
    > ------------
    > Got answer (115 bytes):
    > HEADER:
    > opcode = QUERY, id = 43558, rcode = NOERROR
    > header flags: response, auth. answer, want recursion,
    > recursion avail.
    > questions = 1, answers = 1, authority records = 1,
    > additional = 0
    >
    > QUESTIONS:
    > 1.1.168.192.in-addr.arpa, type = PTR, class = IN
    > ANSWERS:
    > -> 1.1.168.192.in-addr.arpa
    > type = PTR, class = IN, dlen = 25
    > name = ns.advanced-science.com
    > ttl = 10800 (3H)
    > AUTHORITY RECORDS:
    > -> 1.168.192.in-addr.arpa
    > type = NS, class = IN, dlen = 2
    > nameserver = advanced-science.com
    > ttl = 10800 (3H)
    >
    > ------------
    > Default Server: ns.advanced-science.com
    > Address: 192.168.1.1
    > ***********************************************************************
    > ************
    >
    > If I do the same on my Solaris 9 box I instead get
    >
    > ***********************************************************************
    > ************
    > bash-2.05# nslookup -d2
    > ;; res_nmkquery(QUERY, 1.1.168.192.in-addr.arpa, IN, PTR)
    > ------------
    > SendRequest(), len 42
    > HEADER:
    > opcode = QUERY, id = 49175, rcode = NOERROR
    > header flags: query, want recursion
    > questions = 1, answers = 0, authority records = 0,
    > additional = 0
    >
    > QUESTIONS:
    > 1.1.168.192.in-addr.arpa, type = PTR, class = IN
    >
    > ------------
    > ------------
    > Got answer (139 bytes):
    > HEADER:
    > opcode = QUERY, id = 49175, rcode = NXDOMAIN
    > header flags: response, auth. answer, want recursion,
    > recursion avail.
    > questions = 1, answers = 0, authority records = 1,
    > additional = 0
    >
    > QUESTIONS:
    > 1.1.168.192.in-addr.arpa, type = PTR, class = IN
    > AUTHORITY RECORDS:
    > -> 168.192.in-addr.arpa
    > type = SOA, class = IN, dlen = 65
    > ttl = 10800 (3H)
    > origin = prisoner.iana.org
    > mail addr = hostmaster.root-servers.org
    > serial = 2002040800
    > refresh = 1800 (30M)
    > retry = 900 (15M)
    > expire = 604800 (1W)
    > minimum ttl = 604800 (1W)
    >
    > ------------
    > *** Can't find server name for address 192.168.1.1: Non-existent
    > host/domain
    > *** Default servers are not available
    >
    > It looks like someone else feels responsible for 192.168. I am not
    > sure what this means. Here is my config.
    >
    > /var/named/smartsoft-hl.de.rev
    > $TTL 3h
    > 0.1.168.192.in-addr.arpa. IN SOA merkur.smartsoft-hl.de.
    > root.smartsoft-hl.de. (
    > 2004092410 ; Serial
    > 86400 ; Refresh
    > 7200 ; Retry
    > 604800 ; Expire
    > 86400 ; Minimum
    > )
    >
    > 0.1.168.192.in-addr.arpa. IN NS merkur.smartsoft-hl.de.
    > 1 IN PTR merkur.smartsofzone "0.1.168.192.in-addr.arpa"
    >
    > /etc/named.conf
    > ...
    > zone "1.168.192.in-addr.arpa"
    > {
    > type master;
    > file "smartsoft-hl.de.rev";
    > allow-transfer {
    > local_network;
    > };
    > };
    > ...
    >
    > /etc/resolv.conf
    > domain smartsoft-hl.de
    > search smartsoft-hl.de
    > nameserver 192.168.1.1
    >
    > Any ideas?
    >
    > Thanks,
    >
    > Andreas
    > _______________________________________________
    > sunmanagers mailing list
    > sunmanagers@sunmanagers.org
    > http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: Rich Bonfoey: "JNI FC1-1063 and LSI SANS"

    Relevant Pages

    • Re: The server committed an HTTP protocol violation
      ... with the config setting turned off. ... > I ran into a problem using the HttpWebRequest / HttpWebResponse objects> to retrieve information from a Linksys router. ... > check for invalid http headers. ... If an invalid header is found, ...
      (microsoft.public.dotnet.csharp.general)
    • Re: [SLE] Spam emails in the suse-linux-e
      ... Just had an idea Carlos, in the WU Pine Tech Notes, config and preferences ... while your From: header could be a ... Many MUAs use the Return-Path for envelope sender ...
      (SuSE)
    • Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
      ... > MPTable, version 2.0.15 Linux ... > MP Floating Pointer Structure: ... > MP Config Table Header: ... > MP Config Base Table Entries: ...
      (Linux-Kernel)
    • IAS Cert Failures
      ... Despite what I think is the right config, our IAS connections are failing ... We have identical IAS configs working on other Server 2003 boxes, ... The only difference is the non working server is 2003 SP1. ...
      (microsoft.public.internet.radius)