WingNews logo WingNews GitHub [2]
top | item 30596404

Tell HN: All .fj domains have gone offline

93 points| markdown | 4 years ago

domains.fj

fiji.gov.fj

usp.ac.fj

etc.

http://www.iana.org/domains/root/db/fj.html

49 comments

order
[+] Animats|4 years ago|reply
University of the South Pacific, which runs the DNS servers, [1] is up.

Google's DNS server at 8.8.8.8 is having problems.

Lookup using DNS server of sonic.net, which is a normal DNS server.

    nslookup usp.ac.fj
    Server:  127.0.0.53
    Address: 127.0.0.53#53

    Non-authoritative answer:
    Name: usp.ac.fj
    Address: 144.120.141.80
Lookup with Google DNS:

    nslookup 
    > server 8.8.8.8
    Default server: 8.8.8.8
    Address: 8.8.8.8#53
    > usp.ac.fj
    Server: 8.8.8.8
    Address: 8.8.8.8#53

    ** server can't find usp.ac.fj: SERVFAIL
Checking example.com to make sure Google DNS server is live.

    > example.com
    Server:  8.8.8.8
    Address: 8.8.8.8#53

    Non-authoritative answer:
    Name: example.com
    Address: 93.184.216.34
    Name: example.com
    Address: 2606:2800:220:1:248:1893:25c8:1946
Also fails with 1.1.1.1 DNS server.

The Fiji DNS servers are unreachable, but you can get as far as a router at the University of the South Pacific. So the problem is local to there.

    traceroute 144.120.146.1
    traceroute to 144.120.146.1 (144.120.146.1), 30 hops max, 60 byte packets
    ...
     8  AARNET-PTY.edge5.London1.Level3.net (217.163.113.74)  274.795 ms  274.476 ms  273.781 ms
     9  xe-0-0-0.pe1.a.suv.aarnet.net.au (113.197.15.213)  312.534 ms  311.764 ms  311.766 ms
    10  fastethernet0-0.aarnie.usp.ac.fj (202.158.204.194)  313.356 ms  312.176 ms  312.363 ms
    11  * * *
    12  * * *
[1] https://www.usp.ac.fj/
[+] markdown|4 years ago|reply
> University of the South Pacific, which runs the DNS servers, [1] is up.

Not up from within Fiji. All government websites (and email) are down. Banks, Universities, mobile money wallets, etc.

[+] WelcomeShorty|4 years ago|reply
Oddly enough, right now..:

> server 144.120.141.80 Default server: 144.120.141.80 Address: 144.120.141.80#53 > usp.ac.fj Server: 144.120.141.80 Address: 144.120.141.80#53

* server can't find usp.ac.fj: SERVFAIL

[+] Lascaille|4 years ago|reply
That #10 step isn't on Fiji, Fiji isn't 1ms away from .au
[+] niftich|4 years ago|reply
Fijivillage.com reports: "All websites and apps hosted in Fiji with the dotcom.fj suffix are currently down and this has also affected Vodafone’s M-PAiSA services.

This is due to an outage in the University of the South Pacific hosted dotcom.fj domain." [1][2]

[1] https://www.fijivillage.com/news/All-websites--apps-in-Fiji-...

[2] https://twitter.com/fijivillage/status/1501070675691278339

[+] londons_explore|4 years ago|reply
And this folks is one of the reasons you don't use a 1 minute TTL on your DNS responses...
[+] mike_d|4 years ago|reply
3 of the 5 nameservers for fj are online and responding (they are all anycasted around the world). It looks like connectivity to Fiji itself is what is disrupted.

Two are operated by gransy.com and one by PCH.net (which you should consider donating to and helping random country codes stay online: https://www.pch.net/about/donate).

[+] markdown|4 years ago|reply
It's not connectivity to Fiji. The internet works just fine across the country. Only .fj domains (and email accounts) are affected.
[+] herpderperator|4 years ago|reply
It's true...

  couldn't get address for 'ns4.fj': not found
  couldn't get address for 'ns5.fj': not found
  couldn't get address for 'ns2.fj': not found
  couldn't get address for 'ns1.fj': not found
  couldn't get address for 'ns3.fj': not found
  dig: couldn't get address for 'ns4.fj': no more
[+] adamkochanowicz|4 years ago|reply
Reachable for me.
[+] MaxBarraclough|4 years ago|reply
I'm late to the party, but https://fiji.gov.fj/ worked for me, although it was rather slow to load.

I'm in England, for what that's worth.

[+] markdown|4 years ago|reply
Would you mind saying where in the world you are?
[+] kinow|4 years ago|reply
Not working for me, in New Zealand.
[+] kube-system|4 years ago|reply
This is why I always say you should think twice when choosing a ccTLD if you don’t have a presence there. Not every registry has the same uptime as Verisign.
[+] Tepix|4 years ago|reply
Given the amount of past outages of ccTLDs we've seen (almost none), i'd say this problem is negligible and nothing to worry about.

There is one very recent exception however, the russian plans to partly separate from the internet shortly (especially regarding DNS) could well be an issue.

[+] teddyh|4 years ago|reply
Like I have said before¹²: Neither your registrar nor your chosen TLD registry should be in the habit of suspending domains at the drop of a hat, or be at risk of going out of business suddenly. If you mostly trust your local government, your national ccTLD should suffice. In fact, it should be your default choice unless you have strong indications it does not fulfill the above criteria.

1. https://news.ycombinator.com/item?id=29108933

2. https://news.ycombinator.com/item?id=21614298

[+] markdown|4 years ago|reply
And yet to my knowledge this has never happened before.