KevinM1
August 6th, 2007, 12:57 PM
I'm currently trying to set up hosting for a site called rextrader.com. The domain has been purchased, so it's just a matter of pointing it to the correct nameservers. The nameservers (or at least, their IP addresses) have been given to me by my ISP. So, I believe all I have to do is just rewrite the various config files. Unfortunately, I can't get to my test page when I type www.rextrader.com in my browser. Using the IP address itself works, though.
So, here's what I have so far:
/etc/bind/zones/rextrader.com.db:
// replace example.com with your domain name. do not forget the . after
the domain name!
// Also, replace ns1 with the name of your DNS server
rextrader.com. IN SOA ns1.rextrader.com.
ns2.rextrader.com. admin.rextrader.com.
(
// Do not modify the following lines!
2006081401
28800
3600
604800; <<>> DiG 9.3.4 <<>> www.rextrader.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.rextrader.com. IN A
;; AUTHORITY SECTION:
rextrader.com. 9227 IN SOA dns11.register.com. root.register.com. 2006072707 28800 7200 604800 14400
;; Query time: 18 msec
;; SERVER: 65.175.128.46#53(65.175.128.46)
;; WHEN: Mon Aug 6 12:43:18 2007
;; MSG SIZE rcvd: 91
38400
)
// Replace the following line as necessary:
// ns1 = DNS Server name
// mta = mail server name
// example.com = domain name
rextrader.com. IN NS ns1.rextrader.com.
rextrader.com. IN NS ns2.rextrader.com.
rextrader.com. IN MX 10 mta.rextrader.com.
// Replace the IP address with the right IP addresses.
www IN A 65.175.139.109
//mta IN A 192.168.0.3
ns1 IN A 65.175.128.46
ns2 IN A 65.175.128.47
/etc/bind/zones/rev.139.175.65.in-addr.arpa:
//replace example.com with yoour domain name, ns1 with your DNS server
name.
// The number before IN PTR example.com is the machine address of the
DNS server. in my case, it's 1, as my IP address is 192.168.0.1.
@ IN SOA ns1.rextrader.com. ns2.rextrader.com admin.rextrader.com. (
2006081401;
28800;
604800;
604800;
86400
)
IN NS ns1.rextrader.com.
46 IN NS ns2.rextrader.com.
47 IN PTR rextrader.com
/etc/bind/named.conf.local:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "rextrader.com" {
type master;
file "/etc/bind/zones/rextrader.com.db";
};
zone "139.175.65.in-addr.arpa" {
type master;
file "/etc/bind/zones/rev.139.175.65.in-addr.arpa";
};
/etc/bind/named.conf.options:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.
// query-source address * port 53;
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
65.175.128.46;
65.175.128.47;
};
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
// By default, name servers should only perform recursive domain
// lookups for their direct clients. If recursion is left open
// to the entire Internet, your name server could be used to
// perform distributed denial of service attacks against other
// innocent computers. For more information on DDoS recursion:
// http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0987
allow-recursion { localnets; };
// If you have DNS clients on other subnets outside of your
// server's "localnets", you can explicitly add their networks
// without opening up your server to the Internet at large:
// allow-recursion { localnets; 192.168.0.0/24; };
// If your name server is only listening on 127.0.0.1, consider:
// allow-recursion { 127.0.0.1; };
};
The result of my dig www.rextrader.com command:
; <<>> DiG 9.3.4 <<>> www.rextrader.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.rextrader.com. IN A
;; AUTHORITY SECTION:
rextrader.com. 9227 IN SOA dns11.register.com. root.register.com. 2006072707 28800 7200 604800 14400
;; Query time: 18 msec
;; SERVER: 65.175.128.46#53(65.175.128.46)
;; WHEN: Mon Aug 6 12:43:18 2007
;; MSG SIZE rcvd: 91
It looks like at least the first name server is working, but like I said above, the domain name isn't working. I double checked, and it's not a matter of me forgetting to list them with register.com. I'm stumped. Any ideas?
So, here's what I have so far:
/etc/bind/zones/rextrader.com.db:
// replace example.com with your domain name. do not forget the . after
the domain name!
// Also, replace ns1 with the name of your DNS server
rextrader.com. IN SOA ns1.rextrader.com.
ns2.rextrader.com. admin.rextrader.com.
(
// Do not modify the following lines!
2006081401
28800
3600
604800; <<>> DiG 9.3.4 <<>> www.rextrader.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.rextrader.com. IN A
;; AUTHORITY SECTION:
rextrader.com. 9227 IN SOA dns11.register.com. root.register.com. 2006072707 28800 7200 604800 14400
;; Query time: 18 msec
;; SERVER: 65.175.128.46#53(65.175.128.46)
;; WHEN: Mon Aug 6 12:43:18 2007
;; MSG SIZE rcvd: 91
38400
)
// Replace the following line as necessary:
// ns1 = DNS Server name
// mta = mail server name
// example.com = domain name
rextrader.com. IN NS ns1.rextrader.com.
rextrader.com. IN NS ns2.rextrader.com.
rextrader.com. IN MX 10 mta.rextrader.com.
// Replace the IP address with the right IP addresses.
www IN A 65.175.139.109
//mta IN A 192.168.0.3
ns1 IN A 65.175.128.46
ns2 IN A 65.175.128.47
/etc/bind/zones/rev.139.175.65.in-addr.arpa:
//replace example.com with yoour domain name, ns1 with your DNS server
name.
// The number before IN PTR example.com is the machine address of the
DNS server. in my case, it's 1, as my IP address is 192.168.0.1.
@ IN SOA ns1.rextrader.com. ns2.rextrader.com admin.rextrader.com. (
2006081401;
28800;
604800;
604800;
86400
)
IN NS ns1.rextrader.com.
46 IN NS ns2.rextrader.com.
47 IN PTR rextrader.com
/etc/bind/named.conf.local:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "rextrader.com" {
type master;
file "/etc/bind/zones/rextrader.com.db";
};
zone "139.175.65.in-addr.arpa" {
type master;
file "/etc/bind/zones/rev.139.175.65.in-addr.arpa";
};
/etc/bind/named.conf.options:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.
// query-source address * port 53;
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
65.175.128.46;
65.175.128.47;
};
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
// By default, name servers should only perform recursive domain
// lookups for their direct clients. If recursion is left open
// to the entire Internet, your name server could be used to
// perform distributed denial of service attacks against other
// innocent computers. For more information on DDoS recursion:
// http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0987
allow-recursion { localnets; };
// If you have DNS clients on other subnets outside of your
// server's "localnets", you can explicitly add their networks
// without opening up your server to the Internet at large:
// allow-recursion { localnets; 192.168.0.0/24; };
// If your name server is only listening on 127.0.0.1, consider:
// allow-recursion { 127.0.0.1; };
};
The result of my dig www.rextrader.com command:
; <<>> DiG 9.3.4 <<>> www.rextrader.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.rextrader.com. IN A
;; AUTHORITY SECTION:
rextrader.com. 9227 IN SOA dns11.register.com. root.register.com. 2006072707 28800 7200 604800 14400
;; Query time: 18 msec
;; SERVER: 65.175.128.46#53(65.175.128.46)
;; WHEN: Mon Aug 6 12:43:18 2007
;; MSG SIZE rcvd: 91
It looks like at least the first name server is working, but like I said above, the domain name isn't working. I double checked, and it's not a matter of me forgetting to list them with register.com. I'm stumped. Any ideas?