Just a question regarding the apparent demise of the Gallery DNS registration. I can't resolve gallery.menalto.com through any of my normal DNS servers. Has the domain expired?
I have resorted to putting the IP address in my hosts file.
the name servers for gallery2.org are: ns1.menalto.com and ns2.menalto.com
the name servers for the menalto.com domain are: ns1.menalto.com and ns2.menalto.com
Now, the whois entry for manalto.com contains:
DNS Servers:
ns2.menalto.com
ns1.menalto.com
So far, so good.... or, is it?
Here is a trace for the name lookup using "dig" from my linux box at home....:
Quote:
dig +qr +trace +nosearch gallery.menalto.com
; <<>> DiG 9.3.1 <<>> +qr +trace +nosearch gallery.menalto.com
;; global options: printcmd
. 232408 IN NS F.ROOT-SERVERS.NET.
. 232408 IN NS B.ROOT-SERVERS.NET.
. 232408 IN NS J.ROOT-SERVERS.NET.
. 232408 IN NS K.ROOT-SERVERS.NET.
. 232408 IN NS L.ROOT-SERVERS.NET.
. 232408 IN NS M.ROOT-SERVERS.NET.
. 232408 IN NS I.ROOT-SERVERS.NET.
. 232408 IN NS E.ROOT-SERVERS.NET.
. 232408 IN NS D.ROOT-SERVERS.NET.
. 232408 IN NS A.ROOT-SERVERS.NET.
. 232408 IN NS H.ROOT-SERVERS.NET.
. 232408 IN NS C.ROOT-SERVERS.NET.
. 232408 IN NS G.ROOT-SERVERS.NET.
;; Received 436 bytes from 192.168.111.1#53(192.168.111.1) in 24 ms
menalto.com. 76574 IN NS ns1.menalto.com.
menalto.com. 76574 IN NS ns2.menalto.com.
;; Received 116 bytes from 192.5.5.241#53(F.ROOT-SERVERS.NET) in 30 ms
menalto.com. 70017 IN NS ns1.menalto.com.
menalto.com. 70017 IN NS ns2.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 69953 IN NS ns1.menalto.com.
menalto.com. 69953 IN NS ns2.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 35 ms
menalto.com. 65777 IN NS ns1.menalto.com.
menalto.com. 65777 IN NS ns2.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 32 ms
menalto.com. 70017 IN NS ns2.menalto.com.
menalto.com. 70017 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 27 ms
menalto.com. 70017 IN NS ns1.menalto.com.
menalto.com. 70017 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 70017 IN NS ns2.menalto.com.
menalto.com. 70017 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 30 ms
menalto.com. 96809 IN NS ns1.menalto.com.
menalto.com. 96809 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 70016 IN NS ns1.menalto.com.
menalto.com. 70016 IN NS ns2.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 30 ms
menalto.com. 66322 IN NS ns2.menalto.com.
menalto.com. 66322 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 70016 IN NS ns2.menalto.com.
menalto.com. 70016 IN NS ns1.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 66322 IN NS ns1.menalto.com.
menalto.com. 66322 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 76573 IN NS ns2.menalto.com.
menalto.com. 76573 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 76573 IN NS ns1.menalto.com.
menalto.com. 76573 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 65776 IN NS ns2.menalto.com.
menalto.com. 65776 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 69952 IN NS ns2.menalto.com.
menalto.com. 69952 IN NS ns1.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 65776 IN NS ns1.menalto.com.
menalto.com. 65776 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 65776 IN NS ns2.menalto.com.
menalto.com. 65776 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 66322 IN NS ns2.menalto.com.
menalto.com. 66322 IN NS ns1.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 66322 IN NS ns1.menalto.com.
menalto.com. 66322 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 70016 IN NS ns1.menalto.com.
menalto.com. 70016 IN NS ns2.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 30 ms
menalto.com. 76573 IN NS ns2.menalto.com.
menalto.com. 76573 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 70016 IN NS ns2.menalto.com.
menalto.com. 70016 IN NS ns1.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 69952 IN NS ns1.menalto.com.
menalto.com. 69952 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 28 ms
menalto.com. 66322 IN NS ns2.menalto.com.
menalto.com. 66322 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 31 ms
menalto.com. 69952 IN NS ns2.menalto.com.
menalto.com. 69952 IN NS ns1.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 28 ms
menalto.com. 65776 IN NS ns1.menalto.com.
menalto.com. 65776 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 65776 IN NS ns2.menalto.com.
menalto.com. 65776 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 70016 IN NS ns1.menalto.com.
menalto.com. 70016 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 29 ms
menalto.com. 96808 IN NS ns2.menalto.com.
menalto.com. 96808 IN NS ns1.menalto.com.
;; Received 116 bytes from 209.237.226.156#53(ns1.menalto.com) in 29 ms
menalto.com. 96808 IN NS ns1.menalto.com.
menalto.com. 96808 IN NS ns2.menalto.com.
;; Received 116 bytes from 64.71.137.166#53(ns2.menalto.com) in 30 ms
menalto.com. 66322 IN NS ns1.menalto.com.
menalto.com. 66322 IN NS ns2.menalto.com.
dig: too many lookups
My work server (a different OS - Solaris) does resolve the entry.... with only one hop to each of ns1 and ns2.
I believe what my be my problem is either the TCP not enabled, or the MNAME record being recursive (the SOA record for menalto.com indicates that the primary nameserver is menalto.com).
Anyways, I can't seem to be able to diagnose the problem further, other than to say that the problem may be local to my ISP who may have something messed up or in a funny cache.
Anyway, I can't spend more time on it.
gus
bharat
Joined: 2002-05-21
Posts: 7994
Posted: Sat, 2006-05-06 03:25
Thanks for the report. I did a DNS migration recently, and I didn't mean to make a recursive MNAME record. I didn't catch this right away because it appears to actually work for most boxes, but I updated it 3-4 hours ago and it should be ok now. Can you check again and see if you're still having the problem?
Posts: 13451
No, it works just fine for me. And it does for most people. I've seen people complain though, bit I don't know where to start looking?
h0bbel - Gallery Team
If you found my help useful, please consider donating to Gallery
http://h0bbel.p0ggel.org
Posts: 2
After looking in to it.... here's what's up.
the name servers for gallery2.org are: ns1.menalto.com and ns2.menalto.com
the name servers for the menalto.com domain are: ns1.menalto.com and ns2.menalto.com
Now, the whois entry for manalto.com contains:
DNS Servers:
ns2.menalto.com
ns1.menalto.com
So far, so good.... or, is it?
Here is a trace for the name lookup using "dig" from my linux box at home....:
My work server (a different OS - Solaris) does resolve the entry.... with only one hop to each of ns1 and ns2.
I have tried to figure it out, and ran menalto.com through here:
http://www.dnsreport.com/tools/dnsreport.ch?domain=menalto.com
I believe what my be my problem is either the TCP not enabled, or the MNAME record being recursive (the SOA record for menalto.com indicates that the primary nameserver is menalto.com).
Anyways, I can't seem to be able to diagnose the problem further, other than to say that the problem may be local to my ISP who may have something messed up or in a funny cache.
Anyway, I can't spend more time on it.
gus
Posts: 7994
Thanks for the report. I did a DNS migration recently, and I didn't mean to make a recursive MNAME record. I didn't catch this right away because it appears to actually work for most boxes, but I updated it 3-4 hours ago and it should be ok now. Can you check again and see if you're still having the problem?