Search Again:

Re: New domain doesn''t respond

From: Sigurdur Ragnarsson
Date: Friday, February 28, 1997
Time: 3:39:00 pm

>>I checked the delegation for MasonNeck.com and got the following delegation
>>data:
>>- --cut here--
>>You should check these problems and have them fixed. Until then, users
>>cannot perform a reverse lookup for 206.55.18.134, and may have problems
>>looking up data for masonneck.com.
>
>Thanks Sigurdur. I appreciate the time you took to look into our data. I
>had also done some digs and walks and there is no doubt we have to clean up
>the whole secondary name server thing (progress has already been made). But
>I wonder if that will solve this problem because our in house Macs use the
>same name server that is primary for this domain and we can't get http data.
>Thanks again...
>
>Jim Turney http://Look.net (703) 550-7565 vox
>Webmaster http://ListServe.com (703) 339-5012 fax
>Whole Systems Design, Inc. http://ShoppingCarts.com (888) LookNet sales
>Fairfax County, Virginia http://ThreadedDiscussion.com

I was able to lookup www.masonneck.com without problems:

--cut here--
homer:~> dig www.masonneck.com

; <<>> DiG 2.1 <<>> www.masonneck.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 4, Addit: 3
;; QUESTIONS:
;; www.masonneck.com, type = A, class = IN

;; ANSWERS:
www.MasonNeck.com. 86400 A 206.55.18.134

;; AUTHORITY RECORDS:
MasonNeck.com. 86400 NS PO.Look.net.
MasonNeck.com. 86400 NS ns.mnsinc.com.
MasonNeck.com. 86400 NS Name.Look.net.
MasonNeck.com. 86400 NS ns2.mnsinc.com.

;; ADDITIONAL RECORDS:
PO.Look.net. 86400 A 206.55.18.11
Name.Look.net. 86400 A 206.55.18.14
NS2.MNSINC.COM. 152102 A 206.55.3.11

;; Total query time: 19790 msec
;; FROM: homer.menandmice.is to SERVER: default -- 193.4.171.7
;; WHEN: Fri Feb 28 15:31:40 1997
;; MSG SIZE sent: 35 rcvd: 213

homer:~>
--cut here--

However, I was unable to get any web pages from that host. The host
responded to ping requests indicating that it was up and running, but when
I tried to use my web browse, nothing appeared. I even tried to refer to
it by its IP address (http://206.55.18.134) but that didn't make any
difference.

You might want to double-check the HomeDoor configuration, as this doesn't
seem to be related to DNS.


---
Sigurdur Ragnarsson mailto:siggi@menandmice.com
Men & Mice http://www.menandmice.com/



Messages In This Thread:



Return to Digital Point Solutions' Home Page