Page 1 of 1

GraniteCanyon.com RR Edit (DNS)

Posted: Tue Jan 18, 2005 11:52 pm
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...
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

Posted: Wed Jan 19, 2005 9:07 pm
by wyred
As far as I know, it's impossible. You will need that :2222.

Posted: Thu Jan 20, 2005 1:14 pm
by ast3r3x
wyred wrote:As far as I know, it's impossible. You will need that :2222.
Yeah I figured, I'll just have to host it on a real host somewhere, I just like having all the files on m machine.

Posted: Thu Jan 20, 2005 2:43 pm
by timvw
apache has a proxy/gateway module (don't remember the correct name anymore) or you could write your own with php/curl

client -> public -> home:2222

Posted: Thu Jan 20, 2005 11:24 pm
by ast3r3x
timvw wrote:apache has a proxy/gateway module (don't remember the correct name anymore) or you could write your own with php/curl

client -> public -> home:2222
I'm sorry what? I don't see how this would do it, as the problem is that they can't contact me through port 80. Wouldn't they have to contact me under 80 originally for apache to tell them to use a different port? If that is what I am understanding from you.

Posted: Fri Jan 21, 2005 4:45 am
by timvw
visitors surf to public/gateway and submit request.

and then that public/gateway forwards that request to home:2222 the page, and sends the reply it recieves back to the visitor.


there is an apache mdule that does this a zillion times better ;)

Code: Select all

$request = $_SERVERї'HTTP_REQUEST'];
$home = file_get_contents("http://home:2222/$request");
echo $home;

Posted: Sat Jan 22, 2005 12:26 am
by AGISB
I think that would be mod_proxy

Posted: Tue Jan 25, 2005 9:44 am
by ast3r3x
Well maybe DNS isn't even my problem. It seems that the same people who can't access swigg.net:2222 can't access my website by direct IP xxx.xxx.xxx.xxx:2222 either. Now I'm really stumped on what is causing this. If some people can access it, (people in my local town in pennsylvania, some canadians, some peopel from california...), and some people can't (someone from montana, people in Philadelphia/Pittsburgh PA), what is the problem?

Doesn't the fact that some people can access it mean that everything is setup correctly on my end?

I have little knowledge of the inbetweens of the Internet, but I can't even fathom why some people can't access me with my IP.

Posted: Tue Jan 25, 2005 9:57 am
by timvw
probably a router somewhere that is ill configured....

with traceroute those people could see how their packets are routed.... and see where they disappear....

Posted: Tue Jan 25, 2005 10:02 am
by ast3r3x
Just one router or multiple ones?

Is there nothing I can do with this, or could I hope it will remedy in the following days?

Posted: Tue Jan 25, 2005 5:19 pm
by timvw
with a traceroute you could figure out where your packets get lost.. and then contact the people that own that ip.

i've seen this happening because some networks considered a given ip range not to be in use.

Posted: Fri Jan 28, 2005 7:22 pm
by ast3r3x
Well, I'm not really sure where to go from here because when I trace route from my college library it gets me nowhere past the router, and that wouldn't be what is causing problems for other people.

Most people however have been able to access my site that couldn't, but there are still a few stragglers.

Posted: Fri Jan 28, 2005 11:29 pm
by timvw
some routers may not allow icmp... that's why traceroute doesn't work everywhere...