Slashdot Mirror

← Back to Domains

Domain: ckdhr.com

Stories and comments across the archive that link to ckdhr.com.

Comments · 9

  1. DNS Loc by InvisiBill · · Score: 1 · on How To Clean Up Incorrect Geolocation Information?

    http://www.ckdhr.com/dns-loc/howto.html

    You won't be able to fix it yourself, but the ISP should be able to configure their domain to indicate its proper location. A reverse lookup on your IP should then work as intended.

  2. Re:Here it is. by ckd · · Score: 1 · on The 101 Dumbest Moments in Business

    Just remember, everything Darl says belongs to SCO, must belong to SCO. Because he says so.

    He should know; he's the SCO Miser.

  3. GeoURL by RapaNui · · Score: 1 · on Slashback: :CueCat, Exercise, Wormage

    Reminds me of DNS LOC

    Also, check out RFC 1876 - A Means for Expressing Location Information in the Domain Name System

  4. DNS already has this (to an extent) by blowdart · · Score: 5, Interesting · on GeoURL: We Know Where You Live, Work and Blog!

    Not that anyone uses the DNS LEO entries (RFC 1876).

    This allows DNS names (and thus via rDNS, IPs) to store longitude, latitude, even elevation. (I did have a nice diagram here, but the ever so shit lameness filter said I had too much whitespace). The entries themselves look like this

    loiosh.kei.com. LOC 42 21 43.528 N 71 05 06.284 W 12m
    kei.com. LOC 42 21 43.528 N 71 05 06.284 W 12m 30m
    vrx.net. LOC 43 40 N 79 25 W 30m

    But, of course, DNS on a host doesn't allow for all that stalking you can do should amihotornot start supporting this on a per URL basis ....

  5. RFC1876 seems relevant to this discussion by Nugget · · Score: 2 · on Geographical Borders on the Web
    It seems worthwhile to point out the often-neglected RFC1876 which is an established method of using DNS LOC records to accomplish this sort of thing on a voluntary basis.

    The DNS LOC (location) resource record is designed to make this data available. Using the distributed nature of the Domain Name System, it allows individual organizations to manage their own latitude and longitude information (including the use of deliberately imprecise data when needed for security reasons), while making the data available to all who need it without requiring a single point of failure hosting a large database of location information.

    RFC1876 has been long-championed by these guys. If you're a DNS admin, please consider joining the movement! It's fun and useful to list your LOC.

  6. RFC1876 seems relevant to this discussion by Nugget · · Score: 2 · on Geographical Borders on the Web
    It seems worthwhile to point out the often-neglected RFC1876 which is an established method of using DNS LOC records to accomplish this sort of thing on a voluntary basis.

    The DNS LOC (location) resource record is designed to make this data available. Using the distributed nature of the Domain Name System, it allows individual organizations to manage their own latitude and longitude information (including the use of deliberately imprecise data when needed for security reasons), while making the data available to all who need it without requiring a single point of failure hosting a large database of location information.

    RFC1876 has been long-championed by these guys. If you're a DNS admin, please consider joining the movement! It's fun and useful to list your LOC.

  7. RFC1876 seems relevant to this discussion by Nugget · · Score: 2 · on Geographical Borders on the Web
    It seems worthwhile to point out the often-neglected RFC1876 which is an established method of using DNS LOC records to accomplish this sort of thing on a voluntary basis.

    The DNS LOC (location) resource record is designed to make this data available. Using the distributed nature of the Domain Name System, it allows individual organizations to manage their own latitude and longitude information (including the use of deliberately imprecise data when needed for security reasons), while making the data available to all who need it without requiring a single point of failure hosting a large database of location information.

    RFC1876 has been long-championed by these guys. If you're a DNS admin, please consider joining the movement! It's fun and useful to list your LOC.

  8. Re:Most people are still blind to corporatism by ackthpt · · Score: 2 · on Too Much Corporate Power?

    Most people are too busy eating their Big Macs, watching Must See TV, and buying the latest SUVs to really see what's happening

    Sounds like...

    God sends his spaceships to America, the beautiful
    They land at six o'clock and there we are, the dutiful
    Eating from TV trays, tuned into to Happy Days
    Waiting for World War III while Jesus slaves
    To the mating calls of lawyers in love

    Everything should be designed for maximum entertainment value and replace anything which is there for "our own good"
    Michael Eisner in the Whitehouse, Congress wears mouse hats and sessions open with "M-I-C..."
    WCW in the Pentagon
    Ted Nugent as the Atty General

    Sure... why not...

    Vote Naked 2000

  9. Re:Information from a ping/traceroute? by hburch · · Score: 1 · on Secretive Company Scanning the Net
    DNS LOC is what I believe you're referring to. Look at rfc1876 for more information, or look here.

    If you change the phrase 'comparitvely few' to 'effectively zero,' your statement was correct. Battling the 'it's difficult to determine and update lat/long and not worth it' problem, as well as the 'it's proprietary information where our boxes are at' problem means that DNS LOC is doubtful to be useful.