maintaining data in DNS, was Re: [HECnet] HECnet performance....

Cory Smelosky b4 at gewt.net
Wed Jan 9 09:45:53 PST 2013


On 9 Jan 2013, at 12:43, Dave McGuire <mcguire at neurotica.com> wrote:

On 01/09/2013 10:50 AM, Brian Hechinger wrote:
Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP
address).
I think it's time to come up with something a little better to track all
these.

Thoughts?
  A subdomain under some related domain (perhaps
<sub>.hecnet.update.uu.se?) with the tunnel endpoints as A records?

The problem here is that it isn't searchable. You need to know the A
record name. It would be more useful for me to have it in a db.

You could do an AXFR query for the subdomain. ;)

Did I ever tell you about how I implemented a linked list in TXT
records back in '93?   At one time, Digex' nameservers had the menus for
all the local carry-out restaurants stored, item by item, in the
nameserver.   I wrote a little C program to traverse the linked lists and
print out the menus.

That sounds like an approach /I/ would try. ;)


                            -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA



More information about the Hecnet-list mailing list