There is one problem on the first domain, and two on the second one.
1st problem: bitrunners.com has a whole buch of nameservers, but some of them do not provide records for "ns3.bitrunners.com" and "ns4.bitrunners.com" (they are NOT synchronized and serving the same records as should be):
Code:
minibender:~ kilburn$ host -t NS bitrunners.com
bitrunners.com name server ns1.bitrunners.com.
bitrunners.com name server ns2.bitrunners.com.
bitrunners.com name server ns3.bitrunners.com.
bitrunners.com name server ns4.bitrunners.com.
bitrunners.com name server ns5.bitrunners.com.
bitrunners.com name server ns6.bitrunners.com.
bitrunners.com name server ns7.bitrunners.com.
bitrunners.com name server ns8.bitrunners.com.
bitrunners.com name server ns10.bitrunners.com.
bitrunners.com name server ns9.bitrunners.com.
minibender:~ kilburn$ host -t A ns4.bitrunners.com ns1.bitrunners.com
Using domain server:
Name: ns1.bitrunners.com
Address: 151.1.153.29#53
ns4.bitrunners.com has address 151.1.153.22
minibender:~ kilburn$ host -t A ns4.bitrunners.com ns3.bitrunners.com
Using domain server:
Name: ns3.bitrunners.com
Address: 151.1.153.22#53
Host ns4.bitrunners.com not found: 3(NXDOMAIN)
Thus, as the cilent randomly chooses one of the nameservers and asks to him, some clients will get to "correct" servers (such as ns1.bitrunners.com) and get a proper answer, while others hit a "bad" server (such as ns3.bitrunners.com) and get a host not found error.
This problem is there for both domains, but...
The first domain has IP addresses associated to the nameservers directly on the registry info. This is good, and you should do the same with the second one
Search
Member List
Calendar
Help
