- dns-wg - mailman.ripe.net

DNS WG at the 16th RIPE meeting
by Francis Dupont 18 Aug '93

18 Aug '93

I am collecting the ideas for the DNS WG agenda... Here are some elements: - a second root name server in Europe - IPng support (input needed from IPng (TUBA/SIP/PIP/TPIX) groups) - last BIND software (version 4.9.2 is still beta) Francis.Dupont(a)inria.fr

2 1

About the RIPE database software
by Marten Terpstra 16 Aug '93

16 Aug '93

Oops, Sorry people, the last message about the database software was supposed to have gone to the db-wg in stead of the dns-wg. Not that you cannot try the stuff if you do not want to, but still ... -Marten

1 0

RIPE database beta software
by Marten Terpstra 16 Aug '93

16 Aug '93

Dear all, We finally have some beta software running at the NCC for the database, and we would like you to test some things. We have created an empty test RIPE database on ncc.ripe.net running with the new whois daemon. You can send in updates to: testdb(a)ripe.net It will be processed and incorporated in a test database running on ncc.ripe.net (also a whois daemon running on that database). You should receive a ack mail back (to the Reply-To field, or From: is no Reply-To field present) and you should be able to find it in the whois server immediately. Acks should be send to you within minutes. You can also delete objects in that test database, by simply adding a delete: line to an object. So, person: Marten Terpstra address: RIPE Network Coordination Centre (NCC) address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: Netherlands phone: +31 20 592 5065 fax-no: +31 20 592 5090 e-mail: marten(a)ripe.net nic-hdl: MT2 changed: marten(a)ripe.net 930503 source: RIPE delete: just try and delete this thing should delete this object in the database, if all fields are the same as in the database. The ordering of fields does not matter, just as long as attributes with the same name are in the same order, ie in the object above you cannot change the place of two "address:" fields. Also the place of the delete field does not matter, it can be anywhere in the object. Updating should be very quick, ack mails should be send to you within minutes. Please try some stuff and see what happens. Comments on the format of the ack mail are also appreciated. Currently verbose ack is default ie you get at least a one line ack per object you send in, and the full object if there were errors or warnings. If you send in objects with a source other than RIPE it should complain that this is an unknown source and should refuse the update. -Marten PS All requests are already properly logged so be careful with those deletes ;-) PPS The syntax checker for this test database is VERY strict, simply because there is no manual intervention from the NCC any longer. It may well be that existing objects in the real database are no longer accepted ;-)

1 0

Re: localhost in zonefile?
by Dave Morton 11 Aug '93

11 Aug '93

>> Don't know about HP_UX but it's generally recommeded to have this in so you >> don't get surpises, after all, it's your loopback (local) host and you are >> authorative for it, none else, including root servers. You'll also need a: >> >> IN PTR localhost. >> >> in there as well. > >NO. >First, this PTR record belongs into the zone 0.0.127.in-addr.arpa >(or 127.in-addr.arpa, whichever you prefer) for the address 127.0.0.1 . >Second, it is strongly recommended (see BIND operations guide) not to >let it point to the fake top level domain 'localhost.' but to some >localhost.<my>.<dom>.<ain> . For the latter there should be an A-RR for >the IP-address 127.0.0.1 . Peter, Ok, ok - start again else confusion reigns, mabye I was not explicit and I also forgot the 1 above - the joys of cut and paste. One should run primary for 0.0.127.in-addr.arpa, thus in the named.boot file : primary 0.0.127.in-addr.arpa named.local Also a good idea is to stick this in: ; The following are to prevent really stupid queries from going past this server. ; The zero and broadcast stuff primary 0.IN-ADDR.ARPA null primary 255.IN-ADDR.ARPA broadcast and then in named.local file an SOA and an NS record - in my case same as the origin thus the @: @ IN SOA ecrc.de. hostmaster.ecrc.de. ( 1.3 ;Serial 28800 ;Refresh 7200 ;Retry 604800 ;Expire 86400 ) ;Minimum IN NS ecrc.de. 1 IN PTR localhost. Alternatively stick in instead of the @ line: 0.0.127.in-addr.arpa IN SOA whatever.tld - etc.... The null and broadcast files are essentially the same - only an SOA and an NS record are needed. >To answer the original question: Yes, you should have an entry >localhost A 127.0.0.1 >in your (forward) zone files. Note that the current origin will be appended >to 'localhost' in the example, so you really will produce an entry like >localhost.ucd.ie (if ucd.ie were this current origin) with this. > >Regards, > Peter Ok - all true, and perhaps stick in these as well....... localhost. IN A 127.0.0.1 localhost IN A 127.0.0.1 loghost IN CNAME localhost. Well - it seems to work for me ? Dave

1 0

Re: localhost in zonefile?
by Dave Morton 11 Aug '93

11 Aug '93

> >Gentlebeings - > Forgive the intrusion, but I have a DNS question that I think you should >be able to provide a definitive answer on (something I can't get from other >sources). The question is this: should I have an entry such as > >localhost A 127.0.0.1 > >in a zonefile? This seems to me somewhat silly, but I have seen examples in >various places showing it. Also, I've been told that HP-UX v9 breaks if it isn't >in. Hi Arthur, Don't know about HP_UX but it's generally recommeded to have this in so you don't get surpises, after all, it's your loopback (local) host and you are authorative for it, none else, including root servers. You'll also need a: IN PTR localhost. in there as well. an idea might also be to stick in a: loghost IN CNAME localhost. for the worst case as well. Cheers, Dave

2 1

localhost in zonefile?
by arthur＠midir.ucd.ie 10 Aug '93

10 Aug '93

Gentlebeings - Forgive the intrusion, but I have a DNS question that I think you should be able to provide a definitive answer on (something I can't get from other sources). The question is this: should I have an entry such as localhost A 127.0.0.1 in a zonefile? This seems to me somewhat silly, but I have seen examples in various places showing it. Also, I've been told that HP-UX v9 breaks if it isn't in. I'm not on the discussion list, so I'd appreciate answers to this address. Thanking you all in advance ... - Arthur Green University College Dublin Computing Services Tel: +353 1 706 2456 Fax: + 353 1 283 7077 E-mail: arthur(a)midir.ucd.ie

1 0

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