View Single Post
  #4  
Old 15th October 2005, 17:45
themachine themachine is offline
Senior Member
 
Join Date: Oct 2005
Location: Texas, USA
Posts: 109
Thanks: 0
Thanked 0 Times in 0 Posts
Default ISPs... bleh

Do you have your domain registered as its own name server?

Running dig looks wrong...

# dig +trace forthecode.com

com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
;; Received 492 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 33 ms

forthecode.com. 172800 IN NS server1.forthecode.com.
forthecode.com. 172800 IN NS server2.forthecode.com.
;; Received 108 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 43 ms

=> and then it hangs here <=

dig: Couldn't find server 'server2.forthecode.com': Temporary failure in name resolution

Everything digs back to 'forthecode.com' and then tries to resolve 'server1.forthecode.com' and 'server2.forthecode.com' from your nameserver and fails.

Where as if you look at the difference with my domain...

# dig +trace machinehost.org

;; Received 436 bytes from 64.39.2.170#53(64.39.2.170) in 3 ms

org. 172800 IN NS TLD1.ULTRADNS.NET.
org. 172800 IN NS TLD2.ULTRADNS.NET.
org. 172800 IN NS TLD3.ULTRADNS.org.
org. 172800 IN NS TLD4.ULTRADNS.org.
org. 172800 IN NS TLD5.ULTRADNS.INFO.
org. 172800 IN NS TLD6.ULTRADNS.CO.UK.
;; Received 291 bytes from 128.8.10.90#53(D.ROOT-SERVERS.NET) in 42 ms

machinehost.org. 86400 IN NS ns2.machinehost.org.
machinehost.org. 86400 IN NS ns1.machinehost.org.
;; Received 101 bytes from 204.74.112.1#53(TLD1.ULTRADNS.NET) in 63 ms

machinehost.org. 86400 IN A 66.216.72.110
machinehost.org. 86400 IN NS ns1.machinehost.org.
machinehost.org. 86400 IN NS ns2.machinehost.org.
;; Received 101 bytes from 66.216.72.110#53(ns1.machinehost.org) in 0 ms



I would check that port 53 is accessible from outside your network. If you have access to a webserver or have a friend just run the command:

# nslookup forthecode.com w.x.y.z

w.x.y.z being the IP Address of your home/router/IP that your domain is suppose to be listening on. this way your are specifically querying your server at w.x.y.z and not attempting to resolve forthecode.com across the internet.


-----
# nmap -p 53 68.62.233.157

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-10-15 09:39 CDT
Interesting ports on <dnsname_removed> (68.62.233.157):
PORT STATE SERVICE
53/tcp filtered domain

Nmap finished: 1 IP address (1 host up) scanned in 0.632 seconds

----

# nslookup forthecode.com 68.62.233.157
;; connection timed out; no servers could be reached

# nslookup server1.forthecode.com 68.62.233.157
;; connection timed out; no servers could be reached



You've got something going on there on your side...
Reply With Quote