GraniteCanyon.com RR Edit (DNS)
I'm trying to get set up with granitecanyon.com to act as my DNS, and I've hit a step that I'm horribly confused, and am hoping somebody can help with.
I'm trying to figure it out, but I can't figure a lot of it out. I guess I don't need a lot of this stuff, but I'm not quite sure. I'm curious, is there a way to have it use port :2222 so I don't have to put it on the end in the URL? My ISP blocks port 80.
I'm just trying to get a better DNS so that I can have swigg.net point to my IP address, I'm using 1and1.com, but it's been a week, and not all of my friends can access it, and I believe it's a DNS issue.
The example of the RR (whatever that is) they provide on their site is...
I'm trying to figure it out, but I can't figure a lot of it out. I guess I don't need a lot of this stuff, but I'm not quite sure. I'm curious, is there a way to have it use port :2222 so I don't have to put it on the end in the URL? My ISP blocks port 80.
I'm just trying to get a better DNS so that I can have swigg.net point to my IP address, I'm using 1and1.com, but it's been a week, and not all of my friends can access it, and I believe it's a DNS issue.
The example of the RR (whatever that is) they provide on their site is...
Quote:
coffee.com. IN NS ns1.granitecanyon.com.
coffee.com. IN NS ns2.granitecanyon.com.
; multiple RP records authorize others to submit zone changes
; from the email address in the first field after the RP
; This email address is in DNS-email format. That is,
; the '@' (at-sign) is replaced by '.' (dot or period.)
coffee.com. IN RP juan.tea.com. Juan.Valdez.coffee.com.
coffee.com. IN RP juanita.tea.com. Juanita.Valdez.coffee.com.
Juan.Valdez.coffee.com. IN TXT "Juan Valdez, NIC handle: JUAN123"
Juanita.Valdez.coffee.com. IN TXT "Juanita Valdez, RIPE NIC handle: JUANITA"
; addresses for the canonical names
; Many emailers expect the name localhost to exist
; in a domain with this specific, reserved address.
; 127/8 or 127/255.0.0.0 is the address of LOOPBACK-NET
; 127.0.0.1 is reserved to mean this host on the LOOPBACK-NET
localhost.coffee.com. IN A 127.0.0.1
; The IP addresses below are reserved for networks
; not connected to the InterNet. They are not routable by
; most publicly accessible backbones and are here as an
; example only.
navy.coffee.com. IN A 192.168.0.3
; some useful puns that cannot be CNAMEs because
; they are referenced by MX records, below
mail1.coffee.com. IN A 192.168.0.1
mail2.coffee.com. IN A 192.168.0.2
; an address for the zone itself
coffee.com. IN A 192.168.0.4
; Aliases
; These create a nickname or alias for another name known
; to the DNS, the canonical name, hence CNAME. No other
; records may exist with a name the same as this alias.
; 'Java' is an alias for the canonical name, 'Navy.'
java.coffee.com. IN CNAME navy.coffee.com.
frenchroast.coffee.com. IN CNAME mail1.coffee.com.
hazelnut.coffee.com. IN CNAME mail2.coffee.com.
; MX records
; These direct mail delivery agents, like sendmail,
; at hosts which have agreed to accept email for us.
; This assumes that we've arranged with tea.com and
; uu.net to provide this email service for us in
; advance for coffee.com.
; The token 'EXTREF' directs nslint to allow external references.
; The token 'GLOBALOK' directs nslint to allow global records.
; MX records for a host to be treated specially
navy.coffee.com. IN MX 10 mail1.tea.com. ; EXTREF
navy.coffee.com. IN MX 20 mail2.tea.com. ; EXTREF
navy.coffee.com. IN MX 100 mail.uu.net. ; EXTREF
; global MX records for unspecified members of the zone
*.coffee.com. IN MX 10 mail1.coffee.com. ; GLOBALOK
*.coffee.com. IN MX 20 mail2.coffee.com. ; GLOBALOK
*.coffee.com. IN MX 100 mail.uu.net. ; EXTREF GLOBALOK
; MX records for email addressed to the zone itself
coffee.com. IN MX 10 mail1.coffee.com.
coffee.com. IN MX 20 mail2.coffee.com.
coffee.com. IN MX 100 mail.uu.net. ; EXTREF
coffee.com. IN NS ns1.granitecanyon.com.
coffee.com. IN NS ns2.granitecanyon.com.
; multiple RP records authorize others to submit zone changes
; from the email address in the first field after the RP
; This email address is in DNS-email format. That is,
; the '@' (at-sign) is replaced by '.' (dot or period.)
coffee.com. IN RP juan.tea.com. Juan.Valdez.coffee.com.
coffee.com. IN RP juanita.tea.com. Juanita.Valdez.coffee.com.
Juan.Valdez.coffee.com. IN TXT "Juan Valdez, NIC handle: JUAN123"
Juanita.Valdez.coffee.com. IN TXT "Juanita Valdez, RIPE NIC handle: JUANITA"
; addresses for the canonical names
; Many emailers expect the name localhost to exist
; in a domain with this specific, reserved address.
; 127/8 or 127/255.0.0.0 is the address of LOOPBACK-NET
; 127.0.0.1 is reserved to mean this host on the LOOPBACK-NET
localhost.coffee.com. IN A 127.0.0.1
; The IP addresses below are reserved for networks
; not connected to the InterNet. They are not routable by
; most publicly accessible backbones and are here as an
; example only.
navy.coffee.com. IN A 192.168.0.3
; some useful puns that cannot be CNAMEs because
; they are referenced by MX records, below
mail1.coffee.com. IN A 192.168.0.1
mail2.coffee.com. IN A 192.168.0.2
; an address for the zone itself
coffee.com. IN A 192.168.0.4
; Aliases
; These create a nickname or alias for another name known
; to the DNS, the canonical name, hence CNAME. No other
; records may exist with a name the same as this alias.
; 'Java' is an alias for the canonical name, 'Navy.'
java.coffee.com. IN CNAME navy.coffee.com.
frenchroast.coffee.com. IN CNAME mail1.coffee.com.
hazelnut.coffee.com. IN CNAME mail2.coffee.com.
; MX records
; These direct mail delivery agents, like sendmail,
; at hosts which have agreed to accept email for us.
; This assumes that we've arranged with tea.com and
; uu.net to provide this email service for us in
; advance for coffee.com.
; The token 'EXTREF' directs nslint to allow external references.
; The token 'GLOBALOK' directs nslint to allow global records.
; MX records for a host to be treated specially
navy.coffee.com. IN MX 10 mail1.tea.com. ; EXTREF
navy.coffee.com. IN MX 20 mail2.tea.com. ; EXTREF
navy.coffee.com. IN MX 100 mail.uu.net. ; EXTREF
; global MX records for unspecified members of the zone
*.coffee.com. IN MX 10 mail1.coffee.com. ; GLOBALOK
*.coffee.com. IN MX 20 mail2.coffee.com. ; GLOBALOK
*.coffee.com. IN MX 100 mail.uu.net. ; EXTREF GLOBALOK
; MX records for email addressed to the zone itself
coffee.com. IN MX 10 mail1.coffee.com.
coffee.com. IN MX 20 mail2.coffee.com.
coffee.com. IN MX 100 mail.uu.net. ; EXTREF
Comments
Originally posted by ast3r3x
I'm trying to get set up with granitecanyon.com to act as my DNS, and I've hit a step that I'm horribly confused, and am hoping somebody can help with.
I'm trying to figure it out, but I can't figure a lot of it out. I guess I don't need a lot of this stuff, but I'm not quite sure. I'm curious, is there a way to have it use port :2222 so I don't have to put it on the end in the URL? My ISP blocks port 80.
I'm just trying to get a better DNS so that I can have swigg.net point to my IP address, I'm using 1and1.com, but it's been a week, and not all of my friends can access it, and I believe it's a DNS issue.
The example of the RR (whatever that is) they provide on their site is...
I've got similar problems with my ISP blocking port 80. I used bindery to generate my internal DNS records, maybe that can help you.
I'm also using dyndns.org, along with DNSUpdate and it's proving to be a real champ. I do, however, still have to specify a port number when I give out my URL.