|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
|
|
#1
|
|||
|
|||
|
(LONG) I can find my virtualhosted site on my lan, but not on internet
Okay, so here's some information about what I'm trying to do.
I've interspersed some questions as I go in case some of the work I've done so far is causing my problems. I've also put copious screen output to help answer some questions about what I've tried to debug so far. Please bear with me on this one, as it's my first post on DNS issues. I have set up DNS on my Linux box, and registered that box as a nameserver called ns.fuzzybundles.com. ns.fuzzybundles.com appears to be fine and visible to the internet as shown by dig (dig issued from a 3rd party completely unrelated machine): Code:
ptdl052:>dig ns.fuzzybundles.com ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18446 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;ns.fuzzybundles.com. IN A ;; ANSWER SECTION: ns.fuzzybundles.com. 85146 IN A 12.206.3.66 ;; AUTHORITY SECTION: fuzzybundles.com. 85146 IN NS park7.secureserver.net. fuzzybundles.com. 85146 IN NS park8.secureserver.net. ;; Query time: 23 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 11:24:55 2003 ;; MSG SIZE rcvd: 109 I also have a domain named djradiuspdx.com It's using the following nameservers: Primary: ns.fuzzybundles.com Secondary: ns.tzo.com Currently the secondary is there just to make my registrar happy, as ns.tzo.com doesn't actually know how to give an ip for djradiuspdx. I did that because ns.fuzzybundles.com is my primary, and if it's down, then my website is also down. djradiuspdx.com is intended to be hosted on 12.206.3.66 using virtual hosting (along with other domains after I figure this out the first time). I'll probably also create ns1.fuzzybundles.com eventually, but I'm trying to get this stuff working before I spend more money getting names that I may not need to have. Question 1: Is the fact that I don't have two nameservers that can independently map djradiuspdx.com to an IP a definite showstopper? Now from my in-home LAN (on the ns.fuzzybundles.com machine itself), I can ask for www.djradiuspdx.com and I will get: Code:
[root@localhost named]# dig www.djradiuspdx.com ; <<>> DiG 9.1.3 <<>> www.djradiuspdx.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16648 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;www.djradiuspdx.com. IN A ;; ANSWER SECTION: www.djradiuspdx.com. 86400 IN A 12.206.3.66 ;; AUTHORITY SECTION: djradiuspdx.com. 86400 IN NS ns.fuzzybundles.com. ;; ADDITIONAL SECTION: ns.fuzzybundles.com. 86400 IN A 12.206.3.66 ;; Query time: 2 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Jul 2 11:36:59 2003 ;; MSG SIZE rcvd: 99 So it seems to me that (I think) my DNS is working okay at least in respect to my configuring the named.djradiuspdx.conf file and the entry of a djradiuspdx.conf zone to my named.conf file. However, from the internet, dig will only get me the following: Code:
ptdl052:>dig www.djradiuspdx.com ; <<>> DiG 9.2.1 <<>> www.djradiuspdx.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61893 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.djradiuspdx.com. IN A ;; Query time: 2091 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 12:38:37 2003 ;; MSG SIZE rcvd: 37 Since that didn't get me the IP, I try each hop using dig: Code:
ptdl052:>dig www.djradiuspdx.com +norec ; <<>> DiG 9.2.1 <<>> www.djradiuspdx.com +norec ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56722 ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.djradiuspdx.com. IN A ;; AUTHORITY SECTION: com. 172573 IN NS I.GTLD-SERVERS.NET. com. 172573 IN NS J.GTLD-SERVERS.NET. com. 172573 IN NS K.GTLD-SERVERS.NET. com. 172573 IN NS L.GTLD-SERVERS.NET. com. 172573 IN NS M.GTLD-SERVERS.NET. com. 172573 IN NS A.GTLD-SERVERS.NET. com. 172573 IN NS B.GTLD-SERVERS.NET. com. 172573 IN NS C.GTLD-SERVERS.NET. com. 172573 IN NS D.GTLD-SERVERS.NET. com. 172573 IN NS E.GTLD-SERVERS.NET. com. 172573 IN NS F.GTLD-SERVERS.NET. com. 172573 IN NS G.GTLD-SERVERS.NET. com. 172573 IN NS H.GTLD-SERVERS.NET. ;; Query time: 57 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 12:38:42 2003 ;; MSG SIZE rcvd: 261 ptdl052:>dig www.djradiuspdx.com +norec @B.GTLD-SERVERS.NET. ; <<>> DiG 9.2.1 <<>> www.djradiuspdx.com +norec @B.GTLD-SERVERS.NET. ;; global options: printcmd ;; connection timed out; no servers could be reached So at the GTLD servers level, djradiuspdx.com doesn't point to anything. I pointed djradiuspdx.com to the nameserver ns.fuzzybundles.com about 3 days ago, so I'd think it would have propagated by now. (djradiuspdx.com can be whois'ed to see that it's out there.) QUESTION 2: Is there ANYTHING about my nameserver setup that would cause the GTLD-SERVERS to NOT point djradiuspdx.com to ns.fuzzybundles.com? For example, if the GTLD servers have to pretest that both nameservers for djradiuspdx.com must resolve to an IP before registering the name at that top level, that would be an explanation -- or maybe they just register domains without any testing of the nameservers that will handle requests for IPs for those domains. I don't know that answer. Overall, I'm confused about whether I have a configuration problem on my end which is making djradiuspdx.com not appear on the internet, or if there is some issue causing djradiuspdx.com to not be recorded as pointing to ns.fuzzybundles.com as it's nameserver. I just can't tell right now where the responsiblities of the dns hops lie -- what's my fault (my nameserver or its config files), and what might be a problem with other resources (GTLD servers not recording my info properly). I've managed to teach myself all I've needed to get this far with Linux, apache, virtual hosting, etc, and I'll be darned but I just can't get this nameserver+virtual hosting combination figured out. I'd really appreciate help from someone who can see where I might be off-track. Here's the relevant parts of my named.conf and named.djradiuspdx.com files: Code:
named.conf:
zone "fuzzybundles.com" {
type master;
notify no;
file "named.fuzzybundles.com";
};
zone "djradiuspdx.com" {
type master;
notify no;
file "named.djradiuspdx.com";
};
zone "3.206.12.in-addr.arpa" IN {
type master;
notify no;
file "named.12.206.3";
};
named.fuzzybundles.com
$TTL 86400
@ IN SOA ns.fuzzybundles.com. root.fuzzybundles.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
NS ns ; Inet Address of name server
localhost A 127.0.0.1
ns A 12.206.3.66
www CNAME ns
named.djradiuspdx.com
$TTL 86400
@ IN SOA djradiuspdx.com. root.djradiuspdx.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
NS ns.fuzzybundles.com.
localhost A 127.0.0.1
www A 12.206.3.66
named.12.206.3
$TTL 86400
@ IN SOA ns.fuzzybundles.com. root.fuzzybundles.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS ns.fuzzybundles.com.
66 IN PTR ns.fuzzybundles.com.
Thanks! --DJ Radius |
|
#2
|
||||
|
||||
|
While looking into this, I have been having issues with ns.fuzzybundles.com. It worked a few times, then it wouldn't resolve. It looks like your registrar (I assume that's who you created the ns.fuzzybundles.com record with?) are having issues.
Also, I could not ping 12.206.3.66 a lot of the time, although it worked a few times. It's going to be hard to solve this problem unless you can (a) sort out the issues with ns.fuzzybundles.com and (b) keep 12.206.3.66 alive long enough for me to be able to get my bearings!
__________________
Alex (http://www.alex-greg.com) |
|
#3
|
|||
|
|||
|
UGH, my X-server is freaking out. Let me kill X, and that'll probably help with this.
Okay, X is killed, I'm hoping that ns.fuzzybundles.com behaviour has become normal again as a result. If there's any work you'd like me to do on my end while you poke around with the connections, that's fine with me. Anything to help... --DJ Radius Code:
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
397 root 20 -1 37088 18M 5836 R < 94.6 7.3 8667m X
14827 root 19 19 7224 7220 5804 S N 1.3 2.8 6:06 kmatrix.kss
18563 root 12 0 1080 1080 836 R 0.5 0.4 0:00 top
24955 nobody 9 0 31768 23M 8428 S 0.1 9.5 14:46 lt-ntop
1 root 8 0 120 72 72 S 0.0 0.0 0:04 init
2 root 9 0 0 0 0 SW 0.0 0.0 0:01 keventd
3 root 9 0 0 0 0 SW 0.0 0.0 0:00 kapm-idled
4 root 19 19 0 0 0 SWN 0.0 0.0 0:00 ksoftirqd_CPU0
5 root 9 0 0 0 0 SW 0.0 0.0 0:05 kswapd
6 root 9 0 0 0 0 SW 0.0 0.0 0:00 kreclaimd
7 root 9 0 0 0 0 SW 0.0 0.0 0:01 bdflush
8 root 9 0 0 0 0 SW 0.0 0.0 0:02 kupdated
|
|
#4
|
|||
|
|||
|
That is strange, about the pinging. You can load the web page on that machine by using http://12.206.3.66, so it's still connected to the internet, but I also found that ping wasn't responding nicely (using an online utility that pings from who-knows-where).
--DJ Radius Last edited by DJ Radius : July 2nd, 2003 at 05:07 PM. |
|
#5
|
|||
|
|||
|
Here's some info on the registrar. I bought fuzzybundles.com at godaddy, and configured the domain host information to create ns.fuzzybundles.com located at 12.206.3.66.
Here's some dig info: Code:
ptdl052:>dig ns.fuzzybundles.com ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49580 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;ns.fuzzybundles.com. IN A ;; ANSWER SECTION: ns.fuzzybundles.com. 71440 IN A 12.206.3.66 ;; AUTHORITY SECTION: fuzzybundles.com. 3517 IN NS PARK8.SECURESERVER.NET. fuzzybundles.com. 3517 IN NS PARK7.SECURESERVER.NET. ;; Query time: 31 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 15:13:21 2003 ;; MSG SIZE rcvd: 109 Nothing spectacular above, just that ns.fuzzybundles.com is at my IP address and godaddy's nameservers (park[7-8].secureserver.net) are the ones who provided ns.fuzzybundles.com = 12.206.3.66 Code:
ptdl052:>dig fuzzybundles.com ; <<>> DiG 9.2.1 <<>> fuzzybundles.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50258 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;fuzzybundles.com. IN A ;; ANSWER SECTION: fuzzybundles.com. 3525 IN A 64.202.162.37 ;; AUTHORITY SECTION: fuzzybundles.com. 3525 IN NS PARK7.SECURESERVER.NET. fuzzybundles.com. 3525 IN NS PARK8.SECURESERVER.NET. ;; Query time: 31 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 15:13:13 2003 ;; MSG SIZE rcvd: 106 The above shows fuzzybundles.com resolving to 64.202.162.37 . I'm guessing that is where they take fuzzybundles.com and send it to their own machines to drive the DNS lookup to the ns.fuzzybundles.com nameserver, since that's technically what I've registered with them -- a nameserver -- and not a general website domain. Code:
ptdl052:>dig -x 64.202.162.37 ; <<>> DiG 9.2.1 <<>> -x 64.202.162.37 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45140 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;37.162.202.64.in-addr.arpa. IN PTR ;; ANSWER SECTION: 37.162.202.64.in-addr.arpa. 3485 IN PTR ip-64-202-162-37.secureserver.net. ;; AUTHORITY SECTION: 162.202.64.in-addr.arpa. 3485 IN NS wsc2.jomax.net. 162.202.64.in-addr.arpa. 3485 IN NS wsc1.jomax.net. ;; ADDITIONAL SECTION: wsc1.jomax.net. 92962 IN A 63.241.136.66 wsc2.jomax.net. 92962 IN A 63.241.136.31 ;; Query time: 96 msec ;; SERVER: 137.102.151.30#53(137.102.151.30) ;; WHEN: Wed Jul 2 15:14:24 2003 ;; MSG SIZE rcvd: 167 wsc[1-2].jomax.net is (I think) godaddy's IPs for the nameservers that are supposed to point people looking for fuzzybundles.com to ns.fuzzybundles.com. Not sure if the above info helps at all. --DJ Radius |
|
#6
|
||||
|
||||
|
It looks like the problem is with ns.fuzzybundles.com
I cannot get any information from the authorative server (park7.secureserver.net) about this domain. This server is lame - i.e. it is designated as authorative for a domain, but is not providing DNS information about it (or doesn't seem to from my point of view - I have queried three separate name servers here in the UK for it). You need to get it to provide DNS information for fuzzybundles.com. My dig command outputted this: Code:
[root@vaio root]# dig ns.fuzzybundles.com ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48441 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;ns.fuzzybundles.com. IN A ;; AUTHORITY SECTION: fuzzybundles.com. 2274 IN SOA PARK7.SECURESERVER.NET. dns.jomax.NET. 2003070101 10800 3600 604800 3600 ;; Query time: 30 msec ;; SERVER: 212.23.8.1#53(212.23.8.1) ;; WHEN: Wed Jul 2 23:37:35 2003 ;; MSG SIZE rcvd: 105 [root@vaio root]# Note there is no "answer" section. |
|
#7
|
|||
|
|||
|
I was running the same type of stuff in parallel with you. Since my values are cached here at work I had to query directly to godaddy's nameservers. Here's what I saw:
Code:
ptdl052:>dig ns.fuzzybundles.com +norec @PARK8.SECURESERVER.NET. ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com +norec @PARK8.SECURESERVER.NET. ;; global options: printcmd ;; connection timed out; no servers could be reached -= 9 =- ptdl052:>dig ns.fuzzybundles.com +norec @PARK7.SECURESERVER.NET. ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com +norec @PARK7.SECURESERVER.NET. ;; global options: printcmd ;; connection timed out; no servers could be reached -= 9 =- ptdl052:>dig ns.fuzzybundles.com +norec @wsc1.jomax.NET. ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com +norec @wsc1.jomax.NET. ;; global options: printcmd ;; connection timed out; no servers could be reached -= 9 =- ptdl052:>dig ns.fuzzybundles.com +norec @wsc2.jomax.NET. ; <<>> DiG 9.2.1 <<>> ns.fuzzybundles.com +norec @wsc2.jomax.NET. ;; global options: printcmd ;; connection timed out; no servers could be reached -= 9 =- Seems that none of them are able to give an answer (or not timeout for that matter). I'm going to call godaddy right now and tell them about it. I'll post back here when I'm done. |
|
#8
|
||||
|
||||
|
Update: here is a dnstrace (a tool from djbdns) to ns.fuzzybundles.com from a.gtld-servers.net:
Code:
[root@vaio root]# dnstrace a ns.fuzzybundles.com 192.5.6.30 | dnstracesort 1 ns.fuzzybundles.com 192.5.6.30 172800 A 12.206.3.66 1 ns.fuzzybundles.com 64.202.161.138 NXDOMAIN 1 ns.fuzzybundles.com 64.202.163.10 NXDOMAIN 1 park7.secureserver.net 192.5.6.30 172800 A 64.202.161.138 1 park7.secureserver.net 63.241.136.31 3600 A 64.202.161.138 1 park7.secureserver.net 63.241.136.66 3600 A 64.202.161.138 1 park8.secureserver.net 192.5.6.30 172800 A 64.202.163.10 1 park8.secureserver.net 63.241.136.31 3600 A 64.202.163.10 1 park8.secureserver.net 63.241.136.66 3600 A 64.202.163.10 1 wsc1.jomax.net 192.5.6.30 172800 A 63.241.136.66 1 wsc1.jomax.net 63.241.136.31 3600 A 63.241.136.66 1 wsc1.jomax.net 63.241.136.66 3600 A 63.241.136.66 1 wsc2.jomax.net 192.5.6.30 172800 A 63.241.136.31 1 wsc2.jomax.net 63.241.136.31 3600 A 63.241.136.31 1 wsc2.jomax.net 63.241.136.66 3600 A 63.241.136.31 glue . start A 192.5.6.30 glue . start NS . glue fuzzybundles.com 192.5.6.30 NS park7.secureserver.net glue fuzzybundles.com 192.5.6.30 NS park8.secureserver.net glue jomax.net 192.5.6.30 NS wsc1.jomax.net glue jomax.net 63.241.136.31 NS wsc1.jomax.net glue jomax.net 63.241.136.66 NS wsc1.jomax.net glue jomax.net 192.5.6.30 NS wsc2.jomax.net glue jomax.net 63.241.136.31 NS wsc2.jomax.net glue jomax.net 63.241.136.66 NS wsc2.jomax.net glue ns.fuzzybundles.com 192.5.6.30 A 12.206.3.66 glue park7.secureserver.net 192.5.6.30 A 64.202.161.138 glue park7.secureserver.net 63.241.136.31 A 64.202.161.138 glue park7.secureserver.net 63.241.136.66 A 64.202.161.138 glue park8.secureserver.net 192.5.6.30 A 64.202.163.10 glue park8.secureserver.net 63.241.136.31 A 64.202.163.10 glue park8.secureserver.net 63.241.136.66 A 64.202.163.10 glue secureserver.net 192.5.6.30 NS wsc1.jomax.net glue secureserver.net 63.241.136.31 NS wsc1.jomax.net glue secureserver.net 63.241.136.66 NS wsc1.jomax.net glue secureserver.net 192.5.6.30 NS wsc2.jomax.net glue secureserver.net 63.241.136.31 NS wsc2.jomax.net glue secureserver.net 63.241.136.66 NS wsc2.jomax.net glue wsc1.jomax.net 192.5.6.30 A 63.241.136.66 glue wsc1.jomax.net 63.241.136.31 A 63.241.136.66 glue wsc1.jomax.net 63.241.136.66 A 63.241.136.66 glue wsc2.jomax.net 192.5.6.30 A 63.241.136.31 glue wsc2.jomax.net 63.241.136.31 A 63.241.136.31 glue wsc2.jomax.net 63.241.136.66 A 63.241.136.31 [root@vaio root]# park7.secureserver.net (64.202.161.138) and park8.secureserver.net (64.202.163.10) returned nxdomain when asked about your domain. Since those two are the authorities for fuzzybundles.com, DNS information for this domain won't be visible to the internet. |
|
#9
|
||||
|
||||
|
For comparison (and also because I have to have the 1000th post in the DNS forum
) here is the output of a dnstrace for one of my domains:Code:
[root@vaio root]# dnstrace a a.ns.agreg.com 192.5.6.30 | dnstracesort 1 a.ns.agreg.com 192.5.6.30 172800 A 213.253.22.210 ; root server 1 a.ns.agreg.com 213.253.22.210 259200 A 213.253.22.210 ; authority 1 1 a.ns.agreg.com 213.253.22.211 259200 A 213.253.22.210 ; authority 2 1 b.ns.agreg.com 192.5.6.30 172800 A 213.253.22.211 ; root server 1 b.ns.agreg.com 213.253.22.210 259200 A 213.253.22.211 ; authority 1 1 b.ns.agreg.com 213.253.22.211 259200 A 213.253.22.211 ; authority 2 glue . start A 192.5.6.30 glue . start NS . glue agreg.com 192.5.6.30 NS a.ns.agreg.com glue agreg.com 213.253.22.210 NS a.ns.agreg.com glue agreg.com 213.253.22.211 NS a.ns.agreg.com glue agreg.com 192.5.6.30 NS b.ns.agreg.com glue agreg.com 213.253.22.210 NS b.ns.agreg.com glue agreg.com 213.253.22.211 NS b.ns.agreg.com glue a.ns.agreg.com 192.5.6.30 A 213.253.22.210 glue a.ns.agreg.com 213.253.22.210 A 213.253.22.210 glue a.ns.agreg.com 213.253.22.211 A 213.253.22.210 glue b.ns.agreg.com 192.5.6.30 A 213.253.22.211 glue b.ns.agreg.com 213.253.22.210 A 213.253.22.211 glue b.ns.agreg.com 213.253.22.211 A 213.253.22.211 [root@vaio root]# Yours is much longer because you are using out-of-bailiwick DNS servers - i.e. they are .net servers for a .com domain rather than .com Last edited by alexgreg : July 2nd, 2003 at 05:56 PM. |
|
#10
|
|||
|
|||
|
Alex,
Godaddy said to wait another 24 hours to see what happens. So I'm going to revisit this tomorrow. As for what you mentioned about that NXDOMAIN, I haven't run into that concept yet (I'll look it up now after this post). You said that: Quote:
Does that mean it will NEVER be visible to the internet? That would kind of defeat the purpose of registering. Is it that we're in some sort of limbo state still where park7 and park8 aren't quite ready to return full answers yet? (probably why godaddy seemed to imply that a little more time is needed) --DJ Radius Last edited by DJ Radius : July 2nd, 2003 at 06:02 PM. |
|
#11
|
|||
|
|||
|
Hmm, I guess I can't do anything about their use of the .net servers for the .com domains that people set up with them. Oh well. Congrats on your 1000th. It's like turning miles (km for you) on the odometer... :-)
|
|
#12
|
|||
|
|||
|
I'm going to put this down for today to give the 24-hours benefit of the doubt. Tomorrow after lunch I'll see if anything has improved.
Thanks for your help so far! --DJ Radius http://www.thegnawtychinchilla.com (THIS site does work!) |
|
#13
|
||||
|