- dns-wg - mailman.ripe.net

[staff] [local-ir@ripe.net]signing the roots
by Andrei Robachevsky 01 May '03

01 May '03

Dear colleagues, At the DNS-WG at the last RIPE meeting (RIPE 44) Johan Ihren presented his proposal for an interim scheme for signing the public DNS root. The current version of this Internet-Draft is: draft-ietf-dnsop-interim-signed-root-01.txt The full text of this Internet-Draft can be found at: http://www.ietf.org/internet-drafts/draft-ietf-dnsop-interim-signed-root-01… In the Internet-Draft, a mechanism has been proposed for a first stage of a transition from a unsigned DNS root to a signed root, such that the data in the root zone is accompanied by DNSSEC signatures to allow validation. The process of doing this involves the use of a set of operator keys which are signed by one key signing key, sometimes referred to a "master key". It has been further proposed that these key signing keys be managed by the Regional Internet Registries (RIRs). The proposal states the requirements of the RIRs would be to: * establish a secure out-of-band communication path in collaboration with the signing operators which will be used for authenticated exchange of the unsigned keyset. * periodically generate strong keys using a good random number generator * manage their keys (i.e. use them for signing the operator keyset and keeping the private key appropriately secret) Question: Since this Internet-Draft suggests future action by the RIRs, the RIPE community should discuss this issue and provide feedback to the author. Therefore, the following question is asked: Is this a task that should be performed by the RIPE NCC? Please direct your feedback to dns-wg(a)ripe.net mailing list. Regards, Andrei Robachevsky CTO, RIPE NCC

1 0

views.........please
by Mansoor Ahmed 29 Apr '03

29 Apr '03

Hi, I have a requirment of 2 views one for internal and one for external, the named.conf is very simple, but i am unable to query other domains when doing nslookup from outside, it is replaying root servers only. ------------------------------------------------------------ options { directory "/var/named"; pid-file "/var/named/named.pid"; }; logging { channel sec_channel { file "/var/tmp/named.security"; severity info; }; category security { sec_channel; default_syslog; default_debug; }; }; acl "corpnet" { 10.0.0.1; }; view "internal" { match-clients { "corpnet"; }; recursion yes; zone "." in { type hint; file "root.ca"; }; zone "domain-local" { type slave; file "domain-local.hosts"; allow-transfer { any; }; masters { 216.137.31.87; }; }; }; view "external" { match-clients { any; }; recursion no; zone "." in { type hint; file "root.ca"; }; zone "domain1.com" { type slave; file "domain1.com"; allow-transfer { none; }; masters { 216.137.31.87; }; }; }; Please advice, thanks in advance. Mansoor

1 0

I-D on SRV and whois servers
by Marcos Sanz/Denic 29 Apr '03

29 Apr '03

Hi all, In this version of the draft, Gerhard and I have incorporated comments made in the last WG session: http://www.ietf.org/internet-drafts/draft-sanz-whois-srv-00.txt Feedback and comments are very welcome. On the other hand I'd like to raise the question whether some registry zone administrators would be willing to include SRV records pointing to their whois servers, as .de and .at have done. This would increase the gene pool of the initiative. Regards, Marcos Sanz DENIC eG

1 0

add me
by Mansoor Ahmed 29 Apr '03

29 Apr '03

2 1

Re: views in bind9
by Jim Reid 29 Apr '03

29 Apr '03

Mansoor, your question would probably be better posted to bind9-users(a)isc.org, rather than this mailing list. dns-wg(a)ripe.net is for stuff related to the RIPE DNS Working Group and doesn't usually deal with errors or misunderstandings about named.conf files. If you do post to bind-users, I strongly suggest you provide your named.conf file *exactly* as your name server would see it. [Don't hide domain names or whatever.] That would permit someone on that list to accurately diagnose the problem. My guess is you have syntax errors in named.conf or perhaps you're running a BIND8 name server with a BIND9 configuration file. If it's the former, you can use named-checkconf from BIND9 to find the error. A sample named.conf file which uses views can be found under the tests directory in the BIND9 distribution. This directory contains a test suite for most of the features in BIND9. Here's an outline of how to set up views in BIND9, with an inside view for network 10/8 and an outside view for everything else. options { ...... }; controls { ...... }; view "inside" { match-clients { 10/8; }; zone "." { ....... }; zone "example" { ..... }; }; view "outside" { match-clients { !10/8; }; zone "." { ....... }; zone "example" { ..... }; }; If you have further questions about BIND9 config file syntax, please take them to bind9-users(a)isc.org, not here. And please don't ask me directly. :-)

1 0

32.48.194.in-addr.arpa to 63.48.194.in-addr.arpa
by UTA HostMaster 31 Mar '03

31 Mar '03

hello there seems to be problem with the dns-entries for 32.48.194.in-addr.arpa to 63.48.194.in-addr.arpa. the entries in the RIPE-db have the correct dns (dns1.uta.at / ns1.ooe.gv.at). but the entries in ns.ripe.net show ns1.ooe.gv.at and ns.ooe.gv.at. is there a possibility to correct this without sending the reverse delegations again to auto-inaddr(a)ripe.net? > 63.48.194.in-addr.arpa Server: ns1.ooe.gv.at Address: 194.48.60.9 63.48.194.in-addr.arpa origin = ns1.ooe.gv.at mail addr = domain-admin.ooe.gv.at serial = 2001011600 refresh = 86400 (1D) retry = 7200 (2H) expire = 604800 (1W) minimum ttl = 3600 (1H) 63.48.194.in-addr.arpa nameserver = dns1.uta.at 63.48.194.in-addr.arpa nameserver = ns1.ooe.gv.at ns1.ooe.gv.at internet address = 194.48.60.9 > server ns.ripe.net Default Server: ns.ripe.net Address: 193.0.0.193 > set type=any > 63.48.194.in-addr.arpa Server: ns.ripe.net Address: 193.0.0.193 Authoritative answers can be found from: 63.48.194.in-addr.arpa nameserver = ns1.ooe.gv.at 63.48.194.in-addr.arpa nameserver = ns.ooe.gv.at with best regards ------------------------------------------------------- Peter Steinkellner Engineering & Operations Services UTA Hostmaster UTA Telekom AG Donau-City-Strasse 11 A-1220 Wien T: +43/1/9009-4130 F: +43/1/9009-3967 M: +43/699/1388-4130 mailto:peter.steinkellner@uta.at http://www.uta.at -------------------------------------------------------

2 1

Upgrade of 'NCC.RIPE.NET' - 2003-03-21 13:30-14:00 UTC
by Bruce Campbell 20 Mar '03

20 Mar '03

The RIPE NCC is upgrading a portion of the Hostcount project, 'NCC.RIPE.NET', between 13:30 and 14:00 (UTC) on the 21st of March, 2003 by replacing the hardware with a new machine. Sessions to this machine (updates of hostcount data) will be interrupted during this time. Kind regards, -- Bruce Campbell RIPE Systems/Network Engineer NCC www.ripe.net - PGP562C8B1B Operations/Security

1 0

Slot request for next RIPE Meting: ZoneCheck Tool from French NIC
by Mohsen Souissi 19 Mar '03

19 Mar '03

Hi Jim & Peter, As I told Jim this afternoon, AFNIC would like to present to the DNS community the new version of our ZoneCheck tool (ZoneCheckv2) which allows DNS zone checking with respect to DNS standards. Stephane D'Alu (address Cc'ed) wrote the new version from scratch. It fully supports IPv6 and open to support new technologies such as DNSsec and IDN. Here is the URL of a non-definitive version of our ZoneCheck tool : http://zonecheck.nic.fr/v2/ Should you need any further information, please send an e-mail to Stephane and/or zonecheck(a)nic.fr Thanks beforehand, Mohsen.

1 0

ISC OpenReg 1.0.1 Release
by Joe Abley 17 Mar '03

17 Mar '03

[this message is being copied to multiple mailing lists; apologies in advance for duplicates] The Internet Software Consortium is pleased to announce the first public release of OpenReg, an implementation of a DNS Shared Registry System which supports the Extensible Provisioning Protocol (EPP). For more information, and to download OpenReg, please see: http://www.isc.org/products/OpenReg/ OpenReg is free software, released under a BSD-style licence.

1 0

Upgrade of 'DNS.RIPE.NET' 2003-03-13 13:30-14:00 UTC
by Bruce Campbell 12 Mar '03

12 Mar '03

The RIPE NCC is upgrading its primary nameserver, 'DNS.RIPE.NET', between 13:30 and 14:00 (UTC) on the 13th of March, 2003 by replacing the hardware with a new machine. There will be a short period (on the order of 30 seconds) when queries will not be answered. Most resolvers will simply retry or try another nameserver when this occurs. There is also a small window (on the order of two minutes) where some zones secondaried by 'DNS.RIPE.NET' may appear to go backwards to a previous version (although we will attempt to ensure that all zones are up to date before changing over). This situation will correct itself within a short period of time. For any further questions on the upgrade of this machine, please contact ops(a)ripe.net . Kind regards, -- Bruce Campbell RIPE Systems/Network Engineer NCC www.ripe.net - PGP562C8B1B Operations/Security

1 0