Is it possible to load a DNS record to a server I don't specifically have rights to?

[MichaelD]

Lemme tell you what the deal is.

This URL http://server1.ripplehost.com/cpanel is what I use to get to the control panel of my hosted site.

After IE makes the connection, the "cpanel" changes to "2082." I assume that's the port, right?

Well, where I'm at, I get a "page not found" error. The firewall guys say that 2082 is not blocked, but the reason that I can't get to it is b/c there's no DNS record on the server.

I CAN get to www. ripplehost.com, but not the above URL.

Is there some way I can add a DNS record? I know that on my server at home (W2K Server OS) I can just add a pointer...but here......Something to do with nslookup or something? Help. Thanks.

 

[subflava]

Are you sure the DNS server you're using can't find that address? I get the following IP from one of mine - 66.246.44.78
You can just use that IP to access the website if you really can't find it as a temporary solution. You would just type in "http://66.246.44.78/cpanel"

 

[MichaelD]

Originally posted by: subflava
Are you sure the DNS server you're using can't find that address? I get the following IP from one of mine - 66.246.44.78
You can just use that IP to access the website if you really can't find it as a temporary solution. You would just type in "http://66.246.44.78/cpanel"

Thank you for the suggestion, but that was one of the first things I tried. It's got something to do with Apache, which I know nothing about...if you put in the server1.ripplehost.com w/o the /cpanel at the end, you get the "this is an Apache/SSL page" message. It's that "/cpanel" at the end which gets you to the logn screen. And that /cpanel is what's not going thru onmy end for some reason.

I'm pretty sure that somebody that really knows this stuff knows a workaround. I've tried everything I know. Which ain't much....

 

[Garion]

Put the IP address in your hosts file - That skips DNS entirely. c:\windows\system32\drivers\etc\hosts is the name of the file, with no extension. You should put in there a single line that says..


66.246.44.78 server1.ripplehost.com

Save it, and watch it go. Pretty much the same as editing DNS, just only affects your own PC.

Of course, I hate to say it, but I think your firewall guy is wrong. If you can get to the /cpanel URL, you've already done a DNS lookup, resolved the host and connected to it. If you can get to the :2802, then it's probably a firewall blocking you.

- G

 

[MichaelD]

Originally posted by: Garion
Put the IP address in your hosts file - That skips DNS entirely. c:\windows\system32\drivers\etc\hosts is the name of the file, with no extension. You should put in there a single line that says..


66.246.44.78 server1.ripplehost.com

Save it, and watch it go. Pretty much the same as editing DNS, just only affects your own PC.

Of course, I hate to say it, but I think your firewall guy is wrong. If you can get to the /cpanel URL, you've already done a DNS lookup, resolved the host and connected to it. If you can get to the :2802, then it's probably a firewall blocking you.

- G

Thanks, Garion. I looked at that folder, and it's a bunch of things that just say "file." The icon is a white page w/the Windows symbol on it. How do I add a file? Make a Notepad text file? Just a little more info, please?

 

[Garion]

Go to the Start menu and choose "Run".
At the Command Line, enter:
notepad c:\windows\system32\drivers\etc\hosts

It should prompt if you want to create a new file, which you do. In that blank notepad, enter the line I recommended, save the file, then exit. Your PC should now resolve that DNS record as it sits in your hosts file.

- G

 

[MichaelD]

Originally posted by: Garion
Go to the Start menu and choose "Run".
At the Command Line, enter:
notepad c:\windows\system32\drivers\etc\hosts

It should prompt if you want to create a new file, which you do. In that blank notepad, enter the line I recommended, save the file, then exit. Your PC should now resolve that DNS record as it sits in your hosts file.

- G

Thanks bud! Try it right now.

 

[MichaelD]

Damn. No dice. I tried various things. I tried:

66.246.44.78 server1.ripplehost.com

66.246.44.78 server1.ripplehost.com/cpanel

66.246.44.78 server1.ripplehost.com:2082

None of them worked. I keep getting the "TCP error" box. It's gotta be the firewall. What a disappointment.

Thanks for trying though, Garion.

 

[MichaelD]

Desparation bump.

 

[subflava]

It's got to be the firewall. This has nothing to do with DNS. If you are able to lookup "server1.ripplehost.com" and get an IP address back, it's not DNS. The "/cpanel" part has nothing to do with DNS. Did you tell your administrator that you are trying to connect to port 2082 (ie, they need to allow outgoing on that port)? They probably assume you're talking about port 80 when you tell them "website".

A simple test you can do is to try to connect to that port on the server. Open a command prompt in windows and type "telnet 66.246.44.78 2082". If you get a response or command prompt, then I'd be surprised.

 

[MichaelD]

Originally posted by: subflava
It's got to be the firewall. This has nothing to do with DNS. If you are able to lookup "server1.ripplehost.com" and get an IP address back, it's not DNS. The "/cpanel" part has nothing to do with DNS. Did you tell your administrator that you are trying to connect to port 2082 (ie, they need to allow outgoing on that port)? They probably assume you're talking about port 80 when you tell them "website".

A simple test you can do is to try to connect to that port on the server. Open a command prompt in windows and type "telnet 66.246.44.78 2082". If you get a response or command prompt, then I'd be surprised.

C:\>telnet 66.246.44.78 2082
Connecting To 66.246.44.78 2082...Could not open a connection to host on port 2082
: Connect failed

Thanks. ^^That's the results. So, it IS the firewall then. Now I gotta schmooze some people.

Thanks much, subflava.

 

[Nothinman]

Could not open a connection to host on port 23

Looks to me like it didn't even try the right port...

 

[subflava]

Quote

--------------------------------------------------------------------------------
Could not open a connection to host on port 23
--------------------------------------------------------------------------------



Looks to me like it didn't even try the right port...

Nothinman - Who are you quoting about the port 23? I don't see that anywhere in this thread. If you mean that you tried it yourself and got the above, then that's as it should be. They'd better not be running a telnet host on their webserver
I was telling him to connect to port 2082 (which works for me), not 23.

 

[MichaelD]

Sorry about the confusion. I edited my post when I tried to telnet in. I had originally put a ":" inbetween the IP and the port. I edited it to reflect that I DID try it the right way.

I appreciate everyones' help. I am obviously screwed on this one. :|