A record and PTR no longer match and is required by registrar

[Mark Jeftovic (#fb)]

Why don't you switch your dns2 record to t2.zoneedit.com, should fix it going forward

 

[Drew Degentesh]

Mark,

isnic complains about t2:

thinking.is does not pass ISNIC's tests!


Test results for "T2.ZONEEDIT.COM":
The nameserver ns2.zoneedit.com is not consistently registered in DNS (ns2.zoneedit.com => 162.220.35.30 => t2.zoneedit.com)
The nameserver t2.zoneedit.com is missing from the NS record set for THINKING.IS​

I set my NS to:

NAME SERVER(S)
thinking.is dns1.zoneedit.com
thinking.is t2.zoneedit.com

​

 

[Mark Jeftovic (#fb)]

Ok it passes now.

 

[Golli]

Why don't you switch your dns2 record to t2.zoneedit.com, should fix it going forward

Well,

I still get this message here:

Test results for "DNS1.ZONEEDIT.COM":
The nameserver dns2.zoneedit.com is not consistently registered in DNS (dns2.zoneedit.com => 162.220.35.30 => t2.zoneedit.com)
Test results for "T2.ZONEEDIT.COM":
The nameserver t2.zoneedit.com is missing from the NS record set for BLONDAL.IS

Also,

where can i pay for my subscription, i just bought the credits but can't seem to find where to pay for the DNS zone subscription.

Best regards and thanks one more time in advance

 

[Mark Jeftovic (#fb)]

BLONDAL.IS is still delegated to

nserver: dns1.zoneedit.com
nserver: dns2.zoneedit.com

and the NS recs are

$ host -t ns blondal.is
blondal.is name server dns1.zoneedit.com.
blondal.is name server dns2.zoneedit.com.


switch the NS records in your "DNS SEttings" to

dns1.zoneedit.com and t2.zoneedit.com

 

[Drew Degentesh]

Hi Mark,

Sadly this is rearing it's head again:

Test results for "DNS1.ZONEEDIT.COM":
The nameserver dns1.zoneedit.com is not consistently registered in DNS (dns1.zoneedit.com => 162.220.33.236 => t1.zoneedit.com)
Test results for "T2.ZONEEDIT.COM"

Anything in particular I should do to fix?

 

[sandy]

hi there

Can you try:
ns5.zoneedit.com
ns7.zoneedit.com

thanks
sandy

 

[Drew Degentesh]

Hi Sandy. No dice

Test results for "NS5.ZONEEDIT.COM":
The nameserver ns7.zoneedit.com is not consistently registered in DNS (ns7.zoneedit.com => 198.199.82.247 => pdns2.zoneedit.com)
Test results for "NS7.ZONEEDIT.COM"​

 

[sandy]

yikes... the ,fi and .is registries are certainly very picky on naseserver architecture...

here is a list ... hoping two will work out at the registry.

ns18.zoneedit.com - Miami
ns14.zoneedit.com - Miami
ns9.zoneedit.com - Miami
ns5.zoneedit.com - Miami
dns1.zoneedit.com - Miami
ns11.zoneedit.com - Zurich
ns13.zoneedit.com - Zurich
dns4.zoneedit.com - Zurich
ns8.zoneedit.com - Zurich
ns17.zoneedit.com - Zurich
ns15.zoneedit.com - San Jose
dns2.zoneedit.com - San Jose
ns10.zoneedit.com - San Jose
ns19.zoneedit.com - San Jose

dns3.zoneedit.com - NYC
ns7.zoneedit.com - NYC
ns12.zoneedit.com - NYC
ns16.zoneedit.com - NYC

thanks
sandy

 

[Drew Degentesh]

Sandy,

ns5 and t2 seem to have worked.

I think it wants the PTR record to resolve back to the FQDN of the name server. I ran

dig a <NS>.zoneedit.com +short | nslookup
​

on each NS in your list, and the following are probably bad for the .is registry:

ns11.zoneedit.com -> b.dnsvr.com
dns3.zoneedit.com-> multiple records (ns4 dns4) -- not 3
ns7.zoneedit.com -> pdns2.zoneedit.com
ns12.zoneedit.com -> pdns3.zoneedit.com
ns16.zoneedit.com -> pdns1.zoneedit.com
​

These might be okay, not sure how it feels about mutiple PTR records

dns1.zoneedit.com -> multiple records (ns1 dns1)
dns4.zoneedit.com -> multiple records (ns4 dns4)
dns2.zoneedit.com -> multiple records(ns2 dns2)​