No subject

04-Oct-2001 16:00:46.336 queries: info:
XX+/132.174.47.100/metka-t.oa.oclc.org/SOA/IN
04-Oct-2001 16:00:46.338 response-checks: info: unrelated additional info 
'oa1-server.oa.oclc.org' type A from [132.174.29.60].53


Here's the dig:

net-thing 37 /tftpboot: dig soa metka-t.oa.oclc.org

; <<>> DiG 8.3 <<>> soa metka-t.oa.oclc.org 
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; QUERY SECTION:
;;      metka-t.oa.oclc.org, type = SOA, class = IN

;; AUTHORITY SECTION:
oa.oclc.org.            1H IN SOA       oa1-server.oa.oclc.org.
administrator.oa.oclc.org. (
                                        47625           ; serial
                                        15M             ; refresh
                                        10M             ; retry
                                        1D              ; expiry
                                        15M )           ; minimum


;; ADDITIONAL SECTION:
oa1-server.oa.oclc.org.  1H IN A  132.174.29.60

;; Total query time: 7 msec
;; FROM: net-thing to SERVER: default -- 132.174.47.100
;; WHEN: Thu Oct  4 16:00:46 2001
;; MSG SIZE  sent: 37  rcvd: 114


I don't think that it's something to be concerned with.  And there doesn't
seem to be anything to be done about it.

...Kevin O'Neil



-----Original Message-----
From: Adam Hooper [mailto:adamh at densi.com]
Sent: Tuesday, October 02, 2001 10:15 AM
To: bind-users at isc.org
Subject: "Unrelated Additional Info" from Windows 2000 Active Directory
servers



Hello :)

At our company we have a Linux box, "carbon", running BIND 8.2.4 and serving
the world with lovely DNS information about "domainA" for all to behold. We
also have two Windows 2000 Active Directory servers, both serving out
internal network with lovely DNS information about "domainB". domainA only
includes DNS entries for servers which are visible to the entire world;
domainB includes all the internal computers here (except a few Linux boxes
and the computers we haven't migrated to Windows 2000).

DomainB's computers use "carbon" as their primary DNS server, and so
"carbon" transfers all internal domainB queries/updates to "resin", one of
the Win2k servers. Here's the entry in named.conf:

zone "domainB" {
        type forward;
        check-names ignore;
        forward only;
        forwarders { 192.168.1.202; };
};

The internal win2k server "resin" also handles reverse DNS lookups for
domainB. Here's the entry for that forward in named.conf:

zone "1.168.192.in-addr.arpa" in {
        type forward;
        check-names ignore;
        forward first;
        forwarders { 192.168.1.202; };
        file "rev.1.168.192";
};

All is running well. But when checking out our named log, there is something
slightly odd:

Oct  2 08:54:09 carbon named[595]: unrelated additional info 'resin.domainB'
type A from [192.168.1.202].53
Oct  2 08:55:48 carbon last message repeated 2 times
Oct  2 08:56:57 carbon last message repeated 2 times
Oct  2 09:03:26 carbon last message repeated 2 times
Oct  2 09:09:03 carbon last message repeated 2 times
Oct  2 09:09:03 carbon last message repeated 3 times
Oct  2 09:09:03 carbon named[595]: unrelated additional info 'fca.domainB'
type A from [192.168.1.202].53
Oct  2 09:09:03 carbon named[595]: unrelated additional info 'resin.domainB'
type A from [192.168.1.202].53
Oct  2 09:09:38 carbon last message repeated 24 times
Oct  2 09:21:26 carbon last message repeated 2 times
Oct  2 09:23:19 carbon last message repeated 2 times
Oct  2 09:28:57 carbon last message repeated 2 times
Oct  2 09:31:14 carbon last message repeated 2 times

The Windows 2000 server "resin" also have a bunch of stuff in its DNS log,
but I don't know if it's related or not. It's event ID 3150:

The DNS server wrote version 63 of zone 1.168.192.in-addr.arpa to file
1.168.192.in-addr.arpa.dns.

This also happens too often to be right, especially since the version number
hardly ever increments.

These are the only error messages that ever pop up and I don't know what
they mean or if they're bad. Searching around Google has led me to believe
that 1. this is not a severe error and 2. not many people have seen this
before ;).

Any ideas on what's going wrong? Our DNS knowledge is limited.

Thanks,

Adam Hooper
adamhooper at videotron.ca