O.K, before I stumbled across the excellent tutorial on using GoDaddy Total DNS control, I used the view/modify detail link at the bottom of the GoDaddy hosts summary section to create ns1.506birch.com and ns2.506birch.com and point them at my static IP. Then in the Nameservers section of my domain name (FQDN is 506birch.com) I assigned ns1.506birch.com and ns2.506birch.com respectively as nameservers. I also set ns1.506birch.com and ns2.506birch.com as nameservers in ISP Config > Management > Settings > DNS. Does this procedure have a substantially different effect form the procedures outlined in the tutorial on Total DNS Control? Should I just re-do it using the tutorial? -John P.S. Output of dig from remote host Code: ; <<>> DiG 9.3.1 <<>> ns1.506birch.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24335 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;ns1.506birch.com. IN A ;; ANSWER SECTION: ns1.506birch.com. 172800 IN A 24.121.64.47 ;; AUTHORITY SECTION: 506birch.com. 172800 IN NS ns2.506birch.com. 506birch.com. 172800 IN NS ns1.506birch.com. ;; ADDITIONAL SECTION: ns2.506birch.com. 172800 IN A 24.121.64.47 ;; Query time: 131 msec ;; SERVER: 208.109.96.1#53(208.109.96.1) ;; WHEN: Fri Oct 19 22:09:59 2007 ;; MSG SIZE rcvd: 98 [root@ip-208-109-103-20 ~]# dig ns2.506birch.com ; <<>> DiG 9.3.1 <<>> ns2.506birch.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6270 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;ns2.506birch.com. IN A ;; ANSWER SECTION: ns2.506birch.com. 172768 IN A 24.121.64.47 ;; AUTHORITY SECTION: 506birch.com. 172768 IN NS ns1.506birch.com. 506birch.com. 172768 IN NS ns2.506birch.com. ;; ADDITIONAL SECTION: ns1.506birch.com. 172768 IN A 24.121.64.47 ;; Query time: 10 msec ;; SERVER: 208.109.96.1#53(208.109.96.1) ;; WHEN: Fri Oct 19 22:10:31 2007 ;; MSG SIZE rcvd: 98
A clarification of the previous post ISP Config seems like it would be perfect for my hosting requirements, but I just can’t seem to get it working. I am going on my 4th local installation, and have read back about 4 months in the forums, and still don’t know quite what to do. The basic problem is that domain names don’t resolve outside of my local network. If you enter either of the two names in question: www.506birch.com or www.headgallery.com in a browser, it reports “page not found” and if you ping either one of these, it tries to ping my inside (private) IP address 192.168.55.20. Here is a detailed description of what I have done so far: I installed ISP Config using The Perfect Setup - Ubuntu Feisty Fawn (Ubuntu 7.04) and followed the instructions to the letter. I named my server “506birch” and my FQDN which is registered with GoDaddy is 506birch.com. This makes my server 506birch.506birch.com. My internal server IP is 192.168.55.20, while the static IP of my Linksys router is 24.121.64.47 and I have both port forwarding and DMZ enabled to 192.168.55.20. ISP Config works perfectly from both the private and public IP addresses https://my.ip.add.res:81 and I have specified the following settings: Management > Settings > Server > IP address = 192.168.55.20 Management > Settings > DNS > ns1.506birch.com & ns2.506birch.com And I have created the domain 506birch.com: With the following DNS settings: Then I went to my GoDaddy control panel and set up two new “hosts”: NS1.506BIRCH.COM=24.121.64.47 & NS2.506BIRCH.COM=24.121.64.47 And then set the Custom Nameservers to those hosts for both 506birch.com and headgallery.com: Nameserver1=NS1.506BIRCH.COM Nameserver2=NS2.506BIRCH,COM Any help or ideas on where I messed up sure would be appreciated. -John
Thanks! It's done and made 506birch.com was instantly ping-able. I will wait awhile to see if sites start to resolve. Do I need to do this on each domain after it is created or is there a way to automate the process server-wide? -John
If your server is using a private IP address, then the "Create DNS" and "Create DNS-MX" records will use the private IP address for the DNS records (because the system doesn't know your public IP). In this case I'd advise against using these options and recommend to create DNS records directly in the DNS Manager.
I think I am beginning to understand. Thanks a bunch for your prompt assistance. I can now ping, and my sites are resolving to http://mysite.com but not to www.mysite.com. I thought with an a-record of www exactally the opposite would be true. My Settings DNS for 506birch.com are now: domain (SOA) = 506birch.com IP Address = 24.121.64.47 Nameserver 1 = ns1.506birch.com Nameserver 2 = ns2.506birch.com Records: IP-Adresse Hostname 24.121.64.47 ns1 24.121.64.47 ns2 24.121.64.47 www My Settings DNS for headgallery.com are now: domain (SOA) = headgallery.com IP Address = 24.121.64.47 Nameserver 1 = ns1.506birch.com Nameserver 2 = ns2.506birch.com Records: IP-Adresse Hostname 24.121.64.47 www
