It appears that the DNS propagation for ijnet.net to the new DNS servers has completed. Please let our support department know if you are still experiencing issues with mail not being received due to "host not found" errors.
We’ve had a few customers report that they’re seeing timeouts connecting to eNom’s nameservers, which are what we’re currently using to serve the ijnet.net domain. We aren’t seeing that on any of our networks here, but it’s possible there may be some type of networking issue on a backbone somewhere that’s causing this to happen to certain areas of the world. This is likely contributing to the issues we’ve been seeing regarding name resolution from certain providers.
We’ve switched to a new DNS provider and have put the change in place, though it may take up to 24 hours for the switchover to happen fully. We will be monitoring the change over the next day to make sure there are no issues. When it appears to be fully (or close to it, anyway) complete, we’ll post here to let you know so you can check to see if it resolves the issues some networks have been seeing.
After some further research, we’re still pretty confident that any DNS issues that are being experienced are not on our end. From everything we can see, our DNS servers are all responding properly and are returning the proper IP addresses for our gateways.
A recent DNS cache poisoning vulnerability was announced in the last few weeks, and there are reports of it being exploited in the wild. US-CERT VU#800113 contains details of the vulnerability. We do not know whether this may be impacting certain ISPs DNS servers, but it is a supposition based on the evidence we have available to us at this time.
To show that our DNS is working properly, we’ve used DNS Stuff to compile a report for each of our gateways showing that all the root DNS servers list our DNS servers as authoritative and that each of our DNS servers is returning the proper response for our gateway addresses. Click the link for each gateway to see the report. You can use this report when talking with an ISP about them resolving the issue.
 |
 |
