Path: utzoo!attcan!uunet!munnari.oz.au!metro!usage.csd.unsw.oz.au!ccadfa!cjsv From: cjsv@ccadfa.adfa.oz.au (Christopher JS Vance) Newsgroups: comp.protocols.tcp-ip.domains Subject: DNS glue records and BIND 4.8 Message-ID: <1918@ccadfa.adfa.oz.au> Date: 25 Sep 90 02:25:42 GMT Organization: Computer Centre, University College, UNSW, ADFA, Canberra, Australia Lines: 41 I have a number of domains which I serve as primary: two forward domains, one reverse domain for our class B network and, of course, another reverse domain for net 127. The question I have is in regard to the specification of glue records for servers outside my domains which perform secondary service for me - each of my domains (except 127, of course) has the same list of secondary servers. When the same host is listed as a foreign secondary server in each of my domains, are the glue A records: 1) associated with the zone and host; zone 1 ------- foreign server 1 ---- glue address 1a for 1 \ \-- glue address 1b for 1 \---- foreign server 2 ---- glue address 1 for 2 zone 2 ------- foreign server 1 ---- glue address 1a for 1 \ \-- glue address 1b for 1 \---- foreign server 2 ---- glue address 1 for 2 or 2) associated only with the host. zone 1 ------- foreign server 1 ---- glue address 1a for 1 \/ \-- glue address 1b for 1 /\ zone 2 ------- foreign server 2 ---- glue address 1 for 2 In other words, should I put these glue A records into each zone, or only one? Or alternatively, how does BIND decide what A records to send with my zones when somebody transfers them. Subsidiary question: must these A records be added to a zone or is any legitimate way of holding authoritative A records for these hosts adequate (e.g., by holding a secondary of the zone they are themselves defined in)? If the first case holds, must I add glue records to the reverse domain for my own servers, too, even though the zone should only be held by sites already holding that information as part of my forward zones? -- Christopher