DNS LOC Records

Your entry should read:

tranquility.lan. IN LOC 54 34 48 N 1 13 48 W

And that's from reading this:

3. Master File Format

   The LOC record is expressed in a master file in the following format:

   <owner> <TTL> <class> LOC ( d1 [m1 [s1]] {"N"|"S"} d2 [m2 [s2]]
                               {"E"|"W"} alt["m"] [siz["m"] [hp["m"]
                               [vp["m"]]]] )

   (The parentheses are used for multi-line data as specified in [RFC
   1035] section 5.1.)

   where:

       d1:     [0 .. 90]            (degrees latitude)
       d2:     [0 .. 180]           (degrees longitude)
       m1, m2: [0 .. 59]            (minutes latitude/longitude)
       s1, s2: [0 .. 59.999]        (seconds latitude/longitude)
       alt:    [-100000.00 .. 42849672.95] BY .01 (altitude in meters)
       siz, hp, vp: [0 .. 90000000.00] (size/precision in meters)

   If omitted, minutes and seconds default to zero, size defaults to 1m,
   horizontal precision defaults to 10000m, and vertical precision
   defaults to 10m.  These defaults are chosen to represent typical
   ZIP/postal code area sizes, since it is often easy to find
   approximate geographical location by ZIP/postal code.

Hint: no decimals or negatives. :-)

Wade.

Post #43,920 by pwhysall 6/29/02 4:28:20 PM Reply	DNS LOC Records If my latitude is 54.58, and my longitude is -1.23, how do I form a LOC record for the domain tranquillity.lan ? The RFC is somewhat, erm, difficult to follow. A first effort that doesn't work is: `tranquillity.lan. IN LOC 54.58 N -1.23 E` [link\|http://www.faqs.org/rfcs/rfc1876.html\|RFC1876] Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #44,018 by static 6/30/02 9:47:45 PM Reply	What's the difficulty? Your entry should read: `tranquility.lan. IN LOC 54 34 48 N 1 13 48 W` And that's from reading this: 3. Master File Format The LOC record is expressed in a master file in the following format: <owner> <TTL> <class> LOC ( d1 [m1 [s1]] {"N"\|"S"} d2 [m2 [s2]] {"E"\|"W"} alt["m"] [siz["m"] [hp["m"] [vp["m"]]]] ) (The parentheses are used for multi-line data as specified in [RFC 1035] section 5.1.) where: d1: [0 .. 90] (degrees latitude) d2: [0 .. 180] (degrees longitude) m1, m2: [0 .. 59] (minutes latitude/longitude) s1, s2: [0 .. 59.999] (seconds latitude/longitude) alt: [-100000.00 .. 42849672.95] BY .01 (altitude in meters) siz, hp, vp: [0 .. 90000000.00] (size/precision in meters) If omitted, minutes and seconds default to zero, size defaults to 1m, horizontal precision defaults to 10000m, and vertical precision defaults to 10m. These defaults are chosen to represent typical ZIP/postal code area sizes, since it is often easy to find approximate geographical location by ZIP/postal code. Hint: no decimals or negatives. :-) Wade. "Ah. One of the difficult questions."
Post #44,061 by pwhysall 7/1/02 3:08:52 AM Reply	Gotcha. Twas the no decimals nor negatives bit that threw me :) Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]

Welcome to IWETHEY!