Strange DNS problem with resolving
last three days I have problem with one of my domains, RS.SR.
Nothing has been changed with configuration or name servers, nothing touched, problem appeared to start without any (to me known) reason.
It seems that domain cannot resolve correctly, as my DNS servers (ns1.btgport.net, ns2.btgport.net) are working ok more than a year with current configuration and I havent changed anything with them.
I have tried dnsstuff . com service to see what it reporsts. You should refresh it several times as domain sometimes resolves correctly, sometimes not.
Also I tried several looking glasses and many of them have similar problem with ns1/ns2 rotation.
Here is first dnsstuff output:
=========
Searching for rs.sr A record at c.root-servers.net Got referral to NS1.SR.NET. [took 51 ms]
Searching for rs.sr A record at NS1.SR.NET. Reports no A records (NXDOMAIN). 201ms.
Sorry, I could not continue.
==========
Here is second:
==========
Searching for rs.sr A record at b.root-servers.net Got referral to NS2.SR.NET. [took 99 ms]
Searching for rs.sr A record at NS2.SR.NET. Reports a CACHED answer.
The cached answer makes it impossible to test your DNS timing, sorry!.
Reports an answer.
Record is:
Domain Type Class TTL Answer
rs.sr. A IN 9220 66.90.77.186
rs.sr. NS IN 86400 NS2.BTGPORT.NET.
rs.sr. NS IN 86400 NS1.BTGPORT.NET.
NS2.BTGPORT.NET. A IN 82462 66.90.77.188
NS1.BTGPORT.NET. A IN 82462 66.90.77.187
Sorry, I could not continue.
==========
So it seems that ns1.sr.net is not working as it should do. It seems that there is not problem with ns1/ns2.btgport.net name servers, but with registar's (Dotster) name servers?
Any suggestions?
I tried contacting registar and sr.net administrators, but got no answer or ignorancy. You can tried this with more sr domains (co.sr, register.sr...) and the same happens for some of them.
Thanks for any help.
