The other way around this is to have the nameservers for the domain
to be in an already resolving domain, that way you dont need to worry
about glue. This is very common.
I had already used the second trick earlier today (after posting the
message) and what I did is pointed a "dead" domain I personally had at
the right IP (the other register correctly lets you register/change
nameservers [which no-ip has a form for but it seems to do absulutly
nothing])... now I am stuck with a corporate domain depending on a
domain owned by a single employee (me [even though I am the CTO/COO I
personally think it is inapporiate to do it this way])....
You could, of course, register yet another domain
("ns-istudentunion.org"?) for your corporation.
Tim
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[email protected]"
