It appears that a network problem of some sort has knocked Paraguay's top
level domain off the air. Not surprising when you look at the output for:
whois py-dom
and see this:
NS.CNC.UNA.PY 200.10.228.132
SCE.CNC.UNA.PY 200.10.228.133
If anyone on this list is prepared to make a serious offer of secondary
DNS for this country, then please email the admin contact
gbellas@UCA.EDU.PY and the technical contact hmereles@CNC.UNA.PY.
Of course, neither address will work until they get back on the air...
Anyone in a situation like this, I'm willing to do secondaries
for these sorts of domains, and plan to build a secondary-dns-server
engine that people would be able to send templates to, etc..
IMHO, the internic should not allow any domains to have pri+sec nameserver
in the same /24
- Jared
ns.ripe.net [193.0.0.193] and merapi.switch.ch [130.59.211.10] act as
authoritative (secondary) name servers for PY and its direct generic
subdomains {com,edu,gov,org,net,org}.py. I'm not sure whether these
have been requested to be added to the delegation yet. Anyway, these
things seem to take a long time at InterNIC right now - we have
delegation changes pending ourselves for the CH and LI ccTLDs for
about three weeks.
Anyone in a situation like this, I'm willing to do secondaries
for these sorts of domains, and plan to build a secondary-dns-server
engine that people would be able to send templates to, etc..
Same here; nac.net would be willing to host any secondary DNS for anyone,
specifically TLDs or foreign folks. Foreign to the US, that is 
IMHO, the internic should not allow any domains to have pri+sec nameserver
in the same /24
Amen, except it can be misleading.
NS1.NAC.NET 207.99.0.1
NS2.NAC.NET 207.99.0.2
NS6.NAC.NET 209.123.20.243
Whilst 207.99.0.1 and .2 are on the same /24 (obviously), 207.99.0/24 is
subnetted to 256 /32's, and routed to the machines. Why? So, when a
machine/name-server moves within our network, it doesn't have to be
renumbered.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Atheism is a non-prophet organization. I route, therefore I am.
Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member
Father of the Network and Head Bottle-Washer
Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834
Don't choose a spineless ISP; we have more backbone! http://www.nac.net
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
My point is that you're doing it correctly. If you lose
one of your aggregate blocks, it's not going to cause a problem. Like
for example, if someone else started to announce your /24 or a /19
with your dns servers in it.
You also distribute nameservers geographically, so if you
lose power in a location, you don't die.
- jared