About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Recommendations for DNS

  • To:
  • From:
  • Date: Tue, 22 Sep 1998 09:10:46 -0700 (PDT)
  • Cc:
  • Posted-date: Tue, 22 Sep 1998 09:10:46 -0700 (PDT)

> 
> Bill Manning bmanning@localhost wrote:
> > 
> > >   On top of that, I suggest to clearly describe the requirement to quote 
> > >   any "leading" dot(s) that are *not* supposed to be converted to an '@localhost 
> > >   character. 
> > >   Like in wilfried\.woeber.univie.ac.at !
> > >   
> > >   Wilfried Woeber                :  e-mail: Woeber@localhost
> > 
> > 
> > While this particular hack works, it is a clear violation of the spec.
> > 
> > --bill
> > 
> Which specs? At least this recommendation is part of RFC 1912:
> 
> 2.2 SOA records
> 
>    In the SOA record of every zone, remember to fill in the e-mail
>    address that will get to the person who maintains the DNS at your
>    site (commonly referred to as "hostmaster").  The `@localhost in the e-mail
>    must be replaced by a `.' first.  Do not try to put an `@localhost sign in
>    this address.  If the local part of the address already contains a
>    `.' (e.g., John.Smith@localhost), then you need to quote the `.' by
>    preceding it with `\' character.  (e.g., to become
>    John\.Smith.widget.xx) Alternately (and preferred), you can just use
>    the generic name `hostmaster', and use a mail alias to redirect it to
>    the appropriate persons.  There exists software which uses this field
>    to automatically generate the e-mail address for the zone contact.
>    This software will break if this field is improperly formatted.  It
>    is imperative that this address get to one or more real persons,
>    because it is often used for everything from reporting bad DNS data
>    to reporting security incidents.
> 
> Andreas

Ok, I was overly zelous in my reading of RFC1035.  I like what Dave
has published in RFC1912. 


--bill




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community