DNS problem

From: Johan Abrahamsson (johan.abrahamsson_at_ericsson.REMcomOVE)
Date: 10/26/04

  • Next message: Ian Gregory: "OT: Re: non propagation from UH"
    Date: Tue, 26 Oct 2004 11:16:13 +0200
    
    

    Hej,

    We are trying to set up an internal DNS where a dns lookup will give us
    2 ip-addresses back.
    We have created a directory /var/named and put 3 files there. The files
    are called
    1) domain-info, contains:
    $ORIGIN domain.se.
    localhost 86400 IN A 127.0.0.1
    clustertest 86400 IN A 136.225.122.112
             86400 IN A 136.225.122.206

    2) loopback-domain-info, contains:
    @ IN SOA hostname.domain.se. root.domain.se. (

                                             12345;
                                             43200;
                                             3600;
                                             604800;
                                             86400;
                                             )

             IN NS hostname.domain.se. ; secondary
    1 IN PTR localhost.domain.se.

    3) named.root, contains:
    . IN NS hostname.domain.se.
    hostname.domain.se. IN A 136.225.122.112

    We have also changed the resolv.conf file so it looks like this:
    search domain.se
    nameserver 127.0.0.1

    The last file we have changed is the /etc/named.conf file and it looks
    like this:
    options {
             DIRECTORY "/var/named";
    };
    zone "." in {
             type hint;
             file "named.root";
    };
    zone "domain.se" in {
             type slave;
             file "domain-info";
             masters {
                     136.225.122.112;
             };
    };
    zone "0.0.127.in-addr.arpa" in {
             type master;
             file "loopback-domain-info";
    };

    After these changes in.named was restarted. This worked in solaris 8
    where the bind version was 8.2.2.
    However in solaris 9 the bind version in 8.3.3 and we can't get it to
    work anymore.

    This is the errors we reveive in the /var/adm/mesasges

    Oct 26 09:40:32 lu10-8 named[12189]: [ID 295310 daemon.notice] starting
    (/etc/named.conf). in.named BIND 8.3.3 Wed Feb 18 23:46:02 PST 2004
    Oct 26 09:40:32 lu10-8 Generic Patch-5.9-May 2002
    Oct 26 09:40:32 lu10-8 named[12189]: [ID 295310 daemon.warning] Zone
    "domain.se" (file domain-info): no SOA RR found
    Oct 26 09:40:32 lu10-8 named[12189]: [ID 295310 daemon.error] slave zone
    "domain.se" (IN) rejected due to errors (serial 0)
    Oct 26 09:40:32 lu10-8 named[12189]: [ID 295310 daemon.warning] Zone
    "0.0.127.in-addr.arpa" (file loopback-domain-info): No default TTL ($TTL
    <value>) set, usin
    g SOA minimum instead
    Oct 26 09:40:32 lu10-8 named[12190]: [ID 295310 daemon.notice] Ready to
    answer queries.
    Oct 26 09:40:32 lu10-8 named-xfer[12191]: [ID 826191 daemon.notice]
    [136.225.122.112] not authoritative for domain.se, SOA query got rcode
    0, aa 0, ancoun
    t 0, aucount 1

    What modifications are needed to get this to work in Solaris 9?

    Best regards,
    Johan


  • Next message: Ian Gregory: "OT: Re: non propagation from UH"

    Relevant Pages

    • Re: Multiple Domain Correct Configuration
      ... You don’t have an internal DNS zone for 456.com ... Is this configuration incorrect? ... When i ping 123.com our internal ip is ... then it sounds like your internal DNS namespace is 123.com. ...
      (microsoft.public.exchange.admin)
    • Re: Multiple Domain Correct Configuration
      ... i see there is a "mail" host A record in the zone 123.com in our dns server ... Is this configuration incorrect? ... then it sounds like your internal DNS namespace is 123.com. ...
      (microsoft.public.exchange.admin)
    • Re: Passing DNS Through DMZ
      ... > We're using Cisco PIX firewall with three interfaces. ... members are only using the internal DNS, ... creating a zone, or using hosts files, but were not sure what type of zone. ... Microsoft Windows MVP - Windows Server - Directory Services ...
      (microsoft.public.win2000.dns)
    • Re: mixing int./ext. dns
      ... users to be able to resolve using my internal dns server. ... currenlty have an AD-integrated zone (mycompany.com is the AD domain name ... without even the implied warranty of merchantability ...
      (microsoft.public.win2000.dns)
    • Re: mixing int./ext. dns
      ... users to be able to resolve using my internal dns server. ... currenlty have an AD-integrated zone (mycompany.com is the AD domain name ... without even the implied warranty of merchantability ...
      (microsoft.public.windows.server.dns)