DNS for cncc.org.uk broken

[alanw]

The CNCC website is up (at both 77.68.72.103 and 77.68.124.52), but the DNS for it is broken: ns1 and ns2 no longer resolve. However ns3 and ns4 resolve (both to the same IP address) and return an IP address for cncc.org.uk. Since the IP addresses of the DNS servers are the same as those of the website, might the hosting provider be in the middle of moving servers?

I'll email Gary next, but with an @cncc.org.uk address, it might not get through.

$ curl -s --resolve "cncc.org.uk:443:77.68.72.103" "https://cncc.org.uk/"  | grep "<title>"
<title>CNCC - Council for the Northern Caving Community</title>

$ curl -s --resolve "cncc.org.uk:443:77.68.124.52" "https://cncc.org.uk/"  | grep "<title>"
<title>CNCC - Council for the Northern Caving Community</title>

$ whois  cncc.org.uk
...
        Expiry date:  19-Jan-2027
...
    Name servers:
        ns1.cfxhosting.co.uk      77.68.124.52
        ns2.cfxhosting.co.uk      77.68.124.52
...
$ dig +short +noshort @77.68.124.52 cncc.org.uk
cncc.org.uk.        86400    IN    A    77.68.124.52

$ dig +trace cncc.org.uk
...
cncc.org.uk.        172800    IN    NS    ns1.cfxhosting.co.uk.
cncc.org.uk.        172800    IN    NS    ns2.cfxhosting.co.uk.
...
couldn't get address for 'ns1.cfxhosting.co.uk': not found
couldn't get address for 'ns2.cfxhosting.co.uk': not found

$ dig ns1.cfxhosting.co.uk
...
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11113

$ dig +short +noshort @ns3.cfxhosting.co.uk cncc.org.uk
cncc.org.uk.        86400    IN    A    77.68.72.103

$ dig +short +noshort @ns4.cfxhosting.co.uk cncc.org.uk
cncc.org.uk.        86400    IN    A    77.68.72.103

 

[GarDouth]

Not quite sure what's going on there. The CNCC website is about to move servers but I've not started it yet, just been setting up the new server. Currently only ns1 and ns2 are in use on cncc. ns3 and ns4 were in use up to about a week ago but have been removed in preparation for the transfer. So it could just be an out of date dns lookup or propagation issue.

I only get a report of ns1 and ns2 in use for any lookup that I try. Both resolve correctly including reverse lookup.

Thanks for noting it but whatever the issue it should be fixed after the transfer.