Search Again: Re: New domain doesn''t respond From: Jim Turney Date: Thursday, March 6, 1997 Time: 7:36:00 am Well, the refusal of MasonNeck.com to respond to http requests ('no DNS entry' errors, etc) was not a QDNSPro problem. The problem was in the HomeDoor entry for this domain, but almost impossible to discover until we installed the HomeDoor 2.0b7 beta. The problem was an invisible space at the beginning of the entry (before http://). Even looking at that entry in the middle of the list on HomeDoor 1.2, the space was not discernable. After we installed HomeDoor 2.0b7, I tried renaming the virtual server for MasonNeck.com (we were trying everything!). When I closed the new entry and edit window I got an error message that told me all URLs must begin with http://, which it appeared to do, but I discovered the leading space and removed it. This new capability in HomeDoor to check entry errors was the only way I think we would have found this error. I think that when we had two other similar mysterious failures to serve a domain during the past year, we were probably having the same problem but never knew it. We cleared the problem before by simply recreating all relevant files and configuration entries regardless of how accurate they appeared. So I guess we would have eventually cleared this one too, but we wouldn't have learned what the nature of the error was that way. With HomeDoor 2.0 I guess this type of error might be a thing of the past anyway. I'm glad this wasn't a QuickDNSPro problem. Men and Mice software seems to be performing flawlessly. Thanks for everyone's help on this...

Messages In This Thread: Re: New domain doesn''t respond by Sigurdur Ragnarsson on Feb 28, 1997 at 3:39:00 pm Re: New domain doesn''t respond by Jody McAlister on Feb 28, 1997 at 7:53:00 pm Re: New domain doesn''t respond by Jim Turney on Mar 6, 1997 at 7:36:00 am