Icelandic registry requires longer TTLs on NS records

[nordurljosahvida]

I recently received this email from the Icelandic [.is] domain registry:

DOMAIN: redacted.is 

REGISTRY-MESSAGE: 

Faulty DNS setup of domain redacted.is 
ISNIC Reykjavik 4. June 2018 

Dear customer. 

The setup of zone redacted.is on its nameservers appears not to 
be according to ISNIC's requirements for .IS delegations. 

Please see https://www.isnic.is/en/domain/req 
for information on these conditions. 

Please make sure that the setup of domain redacted.is is 
according to the above conditions. The domain can be tested 
at any time using 
https://www.isnic.is/en/domain/test?domain=redacted.is 

ISNIC will put on hold domains not fulfilling the delegation requirements 
for extended periods. See article 22 in the .is delegation rules. 
See https://www.isnic.is/en/domain/rules#7 

ISNIC will automatically park the domain if it is still non-compliant 
after being on hold due to technical non-compliance 
for 30 days. See https://www.isnic.is/en/faq#qparking 

This message is generated automatically and sent to 
the domain's DNS hosting provider with copies to the 
domain contacts as registered in the ISNIC WHOIS 
database. 
See https://www.isnic.is/en/whois/search?query=redacted.is 

The domain redacted.is has now been non-compliant for 
2 consecutive weeks. The domain will be suspended 
(removed from the IS zone - put on hold) if the 
problems persists for more than 8 consecutive weeks. 


If the setup of redacted.is has been fixed, we apologize 
for the interruption and thank you. 


PS 
The following errors are registered when ISNIC attempts 
to check the zone for domain redacted.is: 

Test results for "NS1.MB.redacted.IS": 
Time To Live (TTL) for the NS records must be 86400 seconds (24 hours) or longer (Is now 1800 sec) 
Test results for "PUCK.NETHER.NET": 
Time To Live (TTL) for the NS records must be 86400 seconds (24 hours) or longer (Is now 1800 sec) 



Internet a Islandi hf. | Katrinartuni 2, 105 Reykjavik, Iceland | +354 578 2030 | isnic@isnic.is | isnic.is | modernus.is | rix.is 


----------------------------------------------------------------------------------- 
UPDATE NOTIFY - WE RECEIVED A NOTIFY FOR YOUR REQUEST 
-----------------------------------------------------------------------------------

I've edited the file you see in this search query to amend all three instances of 1800 into 86400 [even though probably the first one would have been enough], rebooted, added a random custom DNS record from the webadmin and removed it just to force a refresh, and now the domain shows as correct on the registry's site.

How do we handle specific situations like these?

Thank you

[JoshData]

I think it would be fine to change the value to 86400 for everyone.

[nordurljosahvida]

That would be great. Thank you.

[nordurljosahvida]

@JoshData is this good to be pulled? I've just almost got my domain deleted over this after 8 weeks from the last miab version upgrade to my box ;]

[JoshData]

Please open a pull request.

[nordurljosahvida]

wow that was fast thanks, will do now

[JoshData]

Well I mean after 2.5 years, it's probably long enough :)

[nordurljosahvida]

Thanks ;]