soa.granitecanyon.com setup problem

Mon Oct 4 13:12:34 UTC 1999

	
	The RP record has 2 fields not 1 as you submitted it, also
	the email address should have the "@" mapped to a ".".

	e.g.
	coolnow.com IN	RP hotister.hotmail.com. MISSING.TXT.FIELD.

	Mark

> this simple task (suppose to) wasted my whole weekend. I still can't
> figure out what I did wrong. I keep getting this error message when I
> click on "submit" button:
> 
> Go back and fix these errors:
> nscheck: RP TXT field is missing
> 
> So I click on back, and double check again and again the PP TXT field,
> can't find anything wrong.. here is my file:
> 
> -----
> ; Name Servers
> 
> coolnow.com.  IN  NS ns1.granitecanyon.com.
> coolnow.com.  IN  NS ns2.granitecanyon.com.
> 
> coolnow.com.  IN  RP hotister at hotmail.com.
> 
> hotister.coolnow.com.    IN  TXT "T.T. Lee, NIC handle: TT309"
> 
> ; addresses for the canonical names
> ; Many emailers expect the name localhost to exist
> ; in a domain with this specific, reserved address.
> ; 127/8 or 127/255.0.0.0 is the address of LOOPBACK-NET
> ; 127.0.0.1 is reserved to mean this host on the LOOPBACK-
> 
> localhost.coolnow.com.   IN  A  127.0.0.1
> 
> ; The IP addresses below are reserved for networks
> ; not connected to the InterNet. They are not routable by
> ; most publicly accessible backbones and are here as an
> ; example only.
> -------
> And I read the FAQ again and again, here is what it said:
> 
> =======
> nscheck: RP TXT field is missing
> RP records are always of the following format:
> <name.zone.top-level-zone> IN RP <email address> <TXT RR name>
> 
> where:
> <name.zone.top-level-zone> is the name of the record
> <email address> is an email address in DNS format (with the @ replaced
> by dots)
> <TXT RR name> is the name of an associated TXT record with additional
> contact information about the human being who can respond to problems
> with this zone. Usually this includes a telephone number and/or a NIC
> handle, as assigned by the appropriate registrar (InterNic, ARIN, RIPE
> or APNIC.) These NIC handles are not the same as your userid, and
> cannot be made up.
> ========
> According to the "example" provide by granitecanyon.com, this is what
> it should look like:
> 
> ; Name Servers
> 
> coffee.com.  IN  NS ns1.granitecanyon.com.
> coffee.com.  IN  NS ns2.granitecanyon.com.
> 
> ; multiple RP records authorize others to submit zone changes
> ; from the email address in the first field after the RP
> ; This email address is in DNS-email format. That is,
> ; the '@' (at-sign) is replaced by '.' (dot or period.)
> 
> coffee.com.  IN  RP juan.tea.com. Juan.Valdez.coffee.com.
> coffee.com.  IN  RP juanita.tea.com. Juanita.Valdez.coffee.com.
> 
> Juan.Valdez.coffee.com.    IN  TXT "Juan Valdez,    NIC handle: JUAN123"
> Juanita.Valdez.coffee.com. IN  TXT "Juanita Valdez, RIPE NIC handle:
> JUANITA"
> 
> ; addresses for the canonical names
> ; Many emailers expect the name localhost to exist
> ; in a domain with this specific, reserved address.
> ; 127/8 or 127/255.0.0.0 is the address of LOOPBACK-NET
> ; 127.0.0.1 is reserved to mean this host on the LOOPBACK-NET
> localhost.coffee.com.   IN  A  127.0.0.1
> 
> ; The IP addresses below are reserved for networks
> ; not connected to the InterNet. They are not routable by
> ; most publicly accessible backbones and are here as an
> ; example only.
> 
> navy.coffee.com.  IN  A  192.168.0.3
> 
> ; some useful puns that cannot be CNAMEs because
> ; they are referenced by MX records, below
> 
> mail1.coffee.com. IN  A  192.168.0.1
> mail2.coffee.com. IN  A  192.168.0.2
> 
> ; an address for the zone itself
> 
> coffee.com.       IN  A  192.168.0.4
> 
> ; Aliases
> ; These create a nickname or alias for another name known
> ; to the DNS, the canonical name, hence CNAME. No other
> ; records may exist with a name the same as this alias.
> 
> ; 'Java' is an alias for the canonical name, 'Navy.'
> java.coffee.com.  IN  CNAME  navy.coffee.com.
> 
> frenchroast.coffee.com. IN  CNAME  mail1.coffee.com.
> hazelnut.coffee.com.    IN  CNAME  mail2.coffee.com.
> 
> ; MX records
> 
> ; These direct mail delivery agents, like sendmail,
> ; at hosts which have agreed to accept email for us.
> 
> ; This assumes that we've arranged with tea.com and
> ; uu.net to provide this email service for us in
> ; advance for coffee.com.
> 
> ; The token 'EXTREF' directs nslint to allow external references.
> ; The token 'GLOBALOK' directs nslint to allow global records.
> 
> ; MX records for a host to be treated specially
> navy.coffee.com.  IN  MX  10  mail1.tea.com.	; EXTREF
> navy.coffee.com.  IN  MX  20  mail2.tea.com.	; EXTREF
> navy.coffee.com.  IN  MX  100 mail.uu.net.	; EXTREF
> 
> ; global MX records for unspecified members of the zone
> *.coffee.com.     IN  MX  10  mail1.coffee.com.	; GLOBALOK
> *.coffee.com.     IN  MX  20  mail2.coffee.com.	; GLOBALOK
> *.coffee.com.     IN  MX  100 mail.uu.net.	; EXTREF GLOBALOK
> 
> ; MX records for email addressed to the zone itself
> coffee.com.       IN  MX  10  mail1.coffee.com.
> coffee.com.       IN  MX  20  mail2.coffee.com.
> coffee.com.       IN  MX  100 mail.uu.net.	; EXTREF
> ====
> 
> Could anyone tell me what I did wrong?? Thanks a bunch!!
> 
> 
> Sent via Deja.com http://www.deja.com/
> Before you buy.
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org