Comments on: Site News – connectivity problems fixed! http://www.teleread.com/site-update/site-news-connectivity-problems-fixed/ News & views on e-books, libraries, publishing and related topics Tue, 14 Feb 2012 21:55:20 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Paul Biba http://www.teleread.com/site-update/site-news-connectivity-problems-fixed/comment-page-1/#comment-1037846 Paul Biba Tue, 14 Apr 2009 22:35:39 +0000 http://www.teleread.org/?p=20392#comment-1037846 To be honest, I'm not a network guy and the solution was meaningless to me. Here is what Alex reported to me: your nameservers don't have any IP addresses registered to them (name server A records). Normally the parent name server will list them. These name server A records are also called 'host records' and are usually set by the domain name registrar. It may be very well that some ISPs use this information to do the required recursive lookups for teleread.com and refuse to go further if they don't find the necessary information. So your (or your provider's) next step would be to go to the registrar add NS records for .... To be honest, I’m not a network guy and the solution was meaningless to me. Here is what Alex reported to me:

your nameservers don’t have any IP addresses registered to them (name server A records). Normally the parent name server will list them. These name server A records are also called ‘host records’ and are usually set by the domain name registrar. It may be very well that some ISPs use this information to do the required recursive lookups for teleread.com and refuse to go further if they don’t find the necessary information.

So your (or your provider’s) next step would be to go to the registrar add NS records for ….

]]> By: Logan Kennelly http://www.teleread.com/site-update/site-news-connectivity-problems-fixed/comment-page-1/#comment-1037831 Logan Kennelly Tue, 14 Apr 2009 22:01:09 +0000 http://www.teleread.org/?p=20392#comment-1037831 So what was the problem and solution? The answer might help someone else resolve similar issues in the future. So what was the problem and solution? The answer might help someone else resolve similar issues in the future.

]]>