I would quite happily put the record on my primary and secondary servers
for you.
Just send me the details and I'll set it up for you today.
Hi.
I have been using the za.{net,org} service very happily for quite a
while
now; registered domains include:
kupke.za.net
-- This is for me, MXes my (regular) mail
mattheisen.za.net -- These four
aulenkamp.za.org were
introduced
auli.za.org
for some
greuel.za.org
friends for similar purposes
golf-kambach.za.org -- (Non-profit use for a) Golf Course
gutenberg.za.org -- Grammar school in
this area
Essentially, I could use 212.202.16.191 as static IP address,
GraniteCanyon provided me with secondary DNS services.
The problems are the following ones:
- My ISP has gone bank-rupt, and all mapped IP addresses were
remapped by the new company (resulting in 194.221.170.50 for
me)
- The former IP cannot be accessed anymore.
- GraniteCanyon (their web server) is down for some days now, I
cannot update the information there.
- Registering a nameserver with za.{net,org} requires that its IP
address can be reverse-looked-up. Since this is no longer the
case,
I registered with dyn.ns1.net in order to provide a name exterior
to the desired domain (it's all about "kupke.za.net" primarily).
- Modifying domain information with za.{net,org} requires me to send
a mail from the former contact mail address, which is
"joachim@xxxxxxxxxxxx"; since kupke.za.net resolves (MX) to
212.202.16.191, which is definitely DEAD, I have a chicken-egg
problem. (OK, I do agree that it might have been unwise to supply
an email address depending on its domain; Network Solutions
allow
to use a password instead of 'Mail from' as an auth scheme...)
The host in question has been offline from June 12th to June 15th, and
I
have spent yesterday trying to redelegate the "kupke.za.net" domain.
Effectively, I would be glad still to receive some delayed mail, considering
the
default queue wait time of 7 days at most mail servers. After having
learned
quite something about the difficulties now, I would like to ask the
za.{org,net} operators (e.g. Christiaan Keet?!) if it was possible
to preliminarily
substitute the IP addresses in question (212.202.16.191 by 194.221.170.50)
_by
hand_ in the zone database, at least for allowing me to wait for the
Public
DNS service at GraniteCanyon to come back to life again.
I would be VERY thankful to whomever could solve my problem(s).
Note: Differently to stated on the ZaNiC web pages zone transfers of
za.{org,net} ARE possible (although not from all servers); grepping
for
granitecanyon then yields 118 different domain names relying on that
service. Since I
have heard some people complaining about GraniteCanyon, I officially
offer
my server as a publicly and freely available secondary DNS server for
non-profit domain names.
--
Sincerely,
Joachim Kupke
Sent through Global Message Exchange - http://www.gmx.net
-------------------------------------------------------------------
FreeDNS mailing list
ZA NiC - free domain names
Posts to: freedns@xxxxxx Archive
at http://www.za.net/freedns/