May 1993 - dns-wg - mailman.ripe.net

Re: BIND 4.9
by Erik-Jan.Bos＠SURFnet.nl 19 May '93

19 May '93

Marten, > * Compiling the stuff on SunOS 4.1.3 is without any problems. But I think > * I have a problem running the 4.9 named. > * > * After I type "/usr/etc/in.named", I get the message: > * > * ld.so: libc.so.8: not found > * > * Weird, I would say, since the file "/usr/lib/libc.so.8" is present on the > * system I try it on (and, yes, I also did a "ldconfig" after placing the > * file in /usr/lib). > * > * Does somebody have a clue for me? Thanks for your concern. > > Just compiled the thing, and no problems seen so far. Everything seems to > work just fine. Check what is in file /etc/ld.so.cache (using strings , to > see if it knows libc.so.8. Maybe even you should throw away that cache file, > and run ldconfig as in your rc.* files. Also, libc.so.8 is quite a high number > if you ask me, rebuild the libc a lot ? We're just on 1.7.1. Then again, we > run SunOS 4.1.2, but there's hardly any differences between the two ... I threw away libc.so.8 and rebuilt libc.so (I know have a version number 1.8.4 locally). Everything is working fine now (and ns.surfnet.nl is running 4.9 BIND). Thanks for pointing me into the libc.so itself direction. __ Erik-Jan.

1 0

BIND 4.9
by Erik-Jan.Bos＠SURFnet.nl 19 May '93

19 May '93

DNSsers, I think most of you saw the Paul Vixie announcement of BIND version 4.9. I ftp-ed the .tar.Z file and it all looks very neat, IMHO. Some documentation and tools are also present in the .tar.Z file! Compiling the stuff on SunOS 4.1.3 is without any problems. But I think I have a problem running the 4.9 named. After I type "/usr/etc/in.named", I get the message: ld.so: libc.so.8: not found Weird, I would say, since the file "/usr/lib/libc.so.8" is present on the system I try it on (and, yes, I also did a "ldconfig" after placing the file in /usr/lib). Does somebody have a clue for me? Thanks for your concern. __ Erik-Jan. P.S. In case you missed the Paul Vixie annoucement you can anonymous FTP it from "ftp.nic.surfnet.nl" in the directory "surfnet/net-management/ip/docs" as "bind-4.9.me".

2 1

BIND 4.9 has been released
by RIPE NCC Staff 19 May '93

19 May '93

[Of course you can also find bind 4.9 and the Operations guide on ftp.ripe.net:tools/dns -- Marten] ------- Forwarded Message Seen in the news in comp.protocols.tcp-ip.domains: From: vixie(a)pa.dec.com (Paul A Vixie) Subject: BIND 4.9 has been released Date: 17 May 93 19:42:21 GMT Organization: DEC Network Systems Lab Lines: 40 NNTP-Posting-Host: cognition.pa.dec.com [ this was posted on the bind and namedroppers mailing lists, now here. --vix ] After several years of development and at least one year of testing, BIND 4.9 has finally exited Beta testing and is ready to rock and roll. You can get it from gatekeeper.dec.com via anonymous FTP as /pub/BSD/bind/4.9/4.9.930517.tar.Z (the Bind Operations Guide, substantially improved, is in the same directory, called BOG.psf). This BIND has been the name server running on DECWRL.DEC.COM, UUNET.UU.NET, EUNET.EU.NET, MUNNARI.OZ.AU, and hundreds of other large and small servers, for at least six months. We consider it "stable". Improvements over 4.8.3 are too numerous to list. If you have had any kind of trouble with 4.8.3 (and if you use it, you've had trouble with it, though you may not know this), you should upgrade to 4.9. Operating system vendors are encouraged to include this version of BIND as soon as their release schedules permit; the NSFnet backbone will thank you for it, as will your customers. This BIND includes "dig" (from USC/ISI) and "host" (from Rutgers), as well as a large collection of contributed scripts, utilities, and documentation. The resolver has also been improved. This BIND is known to compile and run on ULTRIX/RISC 4.2-4.3, SunOS 4.1.x, BSD/386 1.0, NeXTstep 3.0, UMIPS/V, HP-UX 8.x, Alpha AXP OSF/1 1.2, and more. This BIND was funded by Digital Equipment Corporation and is hereby released into full public use, subject to the same restrictions as the U C Berkeley Networking 2 ("net2") release. There is a DIGITAL ("DEC") Copyright in each file but it's just noise for the lawyers -- no practical restrictions have been added other than DIGITAL's disclaimer of liability. I (Paul Vixie) was the principle contributor to this release, as well as code librarian and test/release coordinator. However, my efforts would have been wasted without the assistance and participation of the alpha test list, to whom special thanks are given in the new Bind Operations Guide ("BOG"). - -- Paul Vixie, DEC Network Systems Lab Palo Alto, California, USA "Don't be a rebel, or a conformist; <vixie(a)pa.dec.com> decwrl!vixie they're the same thing, anyway. Find <paul(a)vix.com> vixie!paul your own path, and stay on it." -me PS (from Francis Dupont): A copy of it and diffs for NSAP support are available in: nic.switch.ch:/software/sources/network/bind/bind.4.9.930517.tar.Z nic.switch.ch:/software/sources/network/bind/bind.4.9-nsap-diffs ------- End of Forwarded Message

1 0

BIND 4.9 has been released
by Francis Dupont 19 May '93

19 May '93

Seen in the news in comp.protocols.tcp-ip.domains: From: vixie(a)pa.dec.com (Paul A Vixie) Subject: BIND 4.9 has been released Date: 17 May 93 19:42:21 GMT Organization: DEC Network Systems Lab Lines: 40 NNTP-Posting-Host: cognition.pa.dec.com [ this was posted on the bind and namedroppers mailing lists, now here. --vix ] After several years of development and at least one year of testing, BIND 4.9 has finally exited Beta testing and is ready to rock and roll. You can get it from gatekeeper.dec.com via anonymous FTP as /pub/BSD/bind/4.9/4.9.930517.tar.Z (the Bind Operations Guide, substantially improved, is in the same directory, called BOG.psf). This BIND has been the name server running on DECWRL.DEC.COM, UUNET.UU.NET, EUNET.EU.NET, MUNNARI.OZ.AU, and hundreds of other large and small servers, for at least six months. We consider it "stable". Improvements over 4.8.3 are too numerous to list. If you have had any kind of trouble with 4.8.3 (and if you use it, you've had trouble with it, though you may not know this), you should upgrade to 4.9. Operating system vendors are encouraged to include this version of BIND as soon as their release schedules permit; the NSFnet backbone will thank you for it, as will your customers. This BIND includes "dig" (from USC/ISI) and "host" (from Rutgers), as well as a large collection of contributed scripts, utilities, and documentation. The resolver has also been improved. This BIND is known to compile and run on ULTRIX/RISC 4.2-4.3, SunOS 4.1.x, BSD/386 1.0, NeXTstep 3.0, UMIPS/V, HP-UX 8.x, Alpha AXP OSF/1 1.2, and more. This BIND was funded by Digital Equipment Corporation and is hereby released into full public use, subject to the same restrictions as the U C Berkeley Networking 2 ("net2") release. There is a DIGITAL ("DEC") Copyright in each file but it's just noise for the lawyers -- no practical restrictions have been added other than DIGITAL's disclaimer of liability. I (Paul Vixie) was the principle contributor to this release, as well as code librarian and test/release coordinator. However, my efforts would have been wasted without the assistance and participation of the alpha test list, to whom special thanks are given in the new Bind Operations Guide ("BOG"). -- Paul Vixie, DEC Network Systems Lab Palo Alto, California, USA "Don't be a rebel, or a conformist; <vixie(a)pa.dec.com> decwrl!vixie they're the same thing, anyway. Find <paul(a)vix.com> vixie!paul your own path, and stay on it." -me PS (from Francis Dupont): A copy of it and diffs for NSAP support are available in: nic.switch.ch:/software/sources/network/bind/bind.4.9.930517.tar.Z nic.switch.ch:/software/sources/network/bind/bind.4.9-nsap-diffs

1 0

AS information available via DNS
by Tony Bates 12 May '93

12 May '93

Folks, As one of the actions from the last RIPE meeting we have been thinking about a nice way to have an automatic update procedure based on DNS. As a trial for this an auto-script has been been produced that loads current AS derived data into zonefiles under the domain aut-num.ripe.net. This has two very nice features straight away. It allows you to see a list of networks associated with an AS. For example... [mature-tony-1480] host -lt txt as1104.aut-num.ripe.net AS1104.aut-num.ripe.net TXT 192.16.185.0 AS1104.aut-num.ripe.net TXT 192.16.186.0 AS1104.aut-num.ripe.net TXT 192.16.194.0 AS1104.aut-num.ripe.net TXT 192.16.195.0 AS1104.aut-num.ripe.net TXT 192.16.199.0 AS1104.aut-num.ripe.net TXT 192.87.45.0 I currently use TXT records for the zonefiles (suggestions are welcome if something else is more appropriate ?). Also, you can do more interesting things like perhaps generate access-lists.. For Example... [mature-tony-1482] host -lt txt as1104.aut-num.ripe.net | awk '{ printf ("acces s-list 30 permit %s\n", $3)}' access-list 30 permit 192.16.185.0 access-list 30 permit 192.16.186.0 access-list 30 permit 192.16.194.0 access-list 30 permit 192.16.195.0 access-list 30 permit 192.16.199.0 access-list 30 permit 192.87.45.0 and so on. You can also see what ASes are currently in the RIPE database. host -lt ns aut-num.ripe.net aut-num.ripe.net NS mature.ripe.net AS760.aut-num.ripe.net NS mature.ripe.net AS766.aut-num.ripe.net NS mature.ripe.net AS590.aut-num.ripe.net NS mature.ripe.net NONE-LOCAL.aut-num.ripe.net NS mature.ripe.net AS1717.aut-num.ripe.net NS mature.ripe.net AS2107.aut-num.ripe.net NS mature.ripe.net AS2108.aut-num.ripe.net NS mature.ripe.net AS2111.aut-num.ripe.net NS mature.ripe.net AS1205.aut-num.ripe.net NS mature.ripe.net AS786.aut-num.ripe.net NS mature.ripe.net AS2116.aut-num.ripe.net NS mature.ripe.net AS789.aut-num.ripe.net NS mature.ripe.net AS1213.aut-num.ripe.net NS mature.ripe.net AS2119.aut-num.ripe.net NS mature.ripe.net AS1899.aut-num.ripe.net NS mature.ripe.net AS2122.aut-num.ripe.net NS mature.ripe.net AS1739.aut-num.ripe.net NS mature.ripe.net AS1741.aut-num.ripe.net NS mature.ripe.net AS1923.aut-num.ripe.net NS mature.ripe.net AS1752.aut-num.ripe.net NS mature.ripe.net AS1755.aut-num.ripe.net NS mature.ripe.net AS1241.aut-num.ripe.net NS mature.ripe.net AS2148.aut-num.ripe.net NS mature.ripe.net AS137.aut-num.ripe.net NS mature.ripe.net AS1770.aut-num.ripe.net NS mature.ripe.net AS513.aut-num.ripe.net NS mature.ripe.net AS1257.aut-num.ripe.net NS mature.ripe.net AS2004.aut-num.ripe.net NS mature.ripe.net AS517.aut-num.ripe.net NS mature.ripe.net AS679.aut-num.ripe.net NS mature.ripe.net AS1104.aut-num.ripe.net NS mature.ripe.net AS1267.aut-num.ripe.net NS mature.ripe.net AS1274.aut-num.ripe.net NS mature.ripe.net AS1275.aut-num.ripe.net NS mature.ripe.net AS697.aut-num.ripe.net NS mature.ripe.net AS174.aut-num.ripe.net NS mature.ripe.net AS719.aut-num.ripe.net NS mature.ripe.net AS544.aut-num.ripe.net NS mature.ripe.net AS1290.aut-num.ripe.net NS mature.ripe.net AS2380.aut-num.ripe.net NS mature.ripe.net AS2036.aut-num.ripe.net NS mature.ripe.net AS553.aut-num.ripe.net NS mature.ripe.net AS2043.aut-num.ripe.net NS mature.ripe.net AS1324.aut-num.ripe.net NS mature.ripe.net AS559.aut-num.ripe.net NS mature.ripe.net AS378.aut-num.ripe.net NS mature.ripe.net AS1849.aut-num.ripe.net NS mature.ripe.net NONE.aut-num.ripe.net NS mature.ripe.net AS1853.aut-num.ripe.net NS mature.ripe.net AS565.aut-num.ripe.net NS mature.ripe.net AS224.aut-num.ripe.net NS mature.ripe.net AS60.aut-num.ripe.net NS mature.ripe.net The NONE and NONE-LOCAL zones are not currently loaded. The second aspect of this is the possibilty of having an update procedure based on DNS. Here we could delegate the zone to the "guardian" and if we provided a consistency checking tool to avoid conflicts it would be a nice "dynamic" mechanism for updating AS information. We would like to go this way if you feel using DNS is reasonable as opposed to using some form of login/ftp mechanism as previous used for ripe-60 tags and planned for ripe-81. Please let us know your views on this and also please try looking at the information in the aut-num.ripe.net zone. --Tony

2 4

Re: AS information available via DNS
by Tony Bates 06 May '93

06 May '93

"Willem van der Scheun, SARA, +31 20 5923079" <SCHEUN(a)SARA.NL> writes: * Tony, * * This sounds at first sight as a good idea. Fairly dynamic and distributed a * nd * the like. Right. * A remark about the possibility as building access lists and the like. You c * an * do that quite easily of course, but I would like to have one way of buildin * g * access lists (and BGP network lists for that matter) from the RIPE database * . * Currently we are using nlc. I would definitely prefer that we have ONE tool * to * generate the lists. Apart form this other nice solutions may be available. * Talking about this, will te the tool the NCC is working upon (as was report * ed * at the last RIPE), be based on nlc, or is it completely new? Sure - this was only an example of doing things interactively with the information is all. The tools we are working on will be able to make use of nlc also and generate both ASpath lists and network based lists. * * If you delegate zones should this delegation also be put in the AS object l * ike * it is in the domain object? Delegation can not be done to the guardian (I g * uess * that's why you used double quotes). For AS1103 (SURFnet) the guardian is a * alias for a list of responsibles. If you put delegation info in the AS info * , Well the thing is. Whatever way the update is done it will be some form of file maintainence and whether that is here or there, to me at least doesn't make a lot of difference even if it is multiple people maintaining the zone. * should this state nserver as well as zone-c and tech-c? * Possibly if it is decided this is how the update procedure is done. * Willem --T

1 0

RE: AS information available via DNS
by Willem van der Scheun, SARA, +31 20 5923079 06 May '93

06 May '93

Tony, This sounds at first sight as a good idea. Fairly dynamic and distributed and the like. A remark about the possibility as building access lists and the like. You can do that quite easily of course, but I would like to have one way of building access lists (and BGP network lists for that matter) from the RIPE database. Currently we are using nlc. I would definitely prefer that we have ONE tool to generate the lists. Apart form this other nice solutions may be available. Talking about this, will te the tool the NCC is working upon (as was reported at the last RIPE), be based on nlc, or is it completely new? If you delegate zones should this delegation also be put in the AS object like it is in the domain object? Delegation can not be done to the guardian (I guess that's why you used double quotes). For AS1103 (SURFnet) the guardian is a alias for a list of responsibles. If you put delegation info in the AS info, should this state nserver as well as zone-c and tech-c? Willem

1 0

193.in-addr.arpa procedures -> ripe-85
by Marten Terpstra 03 May '93

03 May '93

Folks, The 193.in-addr.arpa delegation procedures have been made into a RIPE document ripe-85. Only changes since version 1.4 are a few typos and cosmetic. You can find it as ftp.ripe.net:ripe/docs/ripe-docs/ripe-85.txt It is now version 1.5. Before asking for a block delegation, please read the document. Cheers, -Marten

1 0