Problems with DNS

hondo · 09-14-2007, 12:31 PM

Hi

I have been setting up a machine with a DNS and a web server. The domain i have is "born2explore.net" and it doesnt seem to work for some weird reason, i cant figure out why.

I have set up port-forwarding for port 80 and 53 as well as 953. I can access the domains fine within the local network, but not on the internet. I have turned off all firewalls i can think off to try to solve the problem. Im running debian 3.1 sarge with bind and apache. When i look at the logs it says that all zones are being loaded and bind is starting to run as well as born2explore.net is sending notifies. There is no syntax errors in the apache config and there doesnt seem to be any problems with apache.

Could someone please help me out here? I cant get "www.born2explore.net" to be visible on the internet and i cant even ping the IP 84.215.5.246 which is the machine's IP adress (it works fine to ping the IP inside the local network).

Thanks for all help.

soroccoheaven · 09-14-2007, 12:51 PM

Quote:

[root@serv root]# dig born2explore.net

; <<>> DiG 9.3.0 <<>> born2explore.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64140
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;born2explore.net. IN A

;; ANSWER SECTION:
born2explore.net. 604800 IN A 84.215.5.246

;; AUTHORITY SECTION:
born2explore.net. 604800 IN NS web01.born2explore.net.

;; ADDITIONAL SECTION:
web01.born2explore.net. 604800 IN A 84.215.5.246

;; Query time: 4651 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Fri Sep 14 23:19:23 2007
;; MSG SIZE rcvd: 86

[root@serv root]#

i think its perfect..

hondo · 09-14-2007, 12:56 PM

Thanks for your reply. Hmm, strange that it doenst work. Do you get the site www.born2explore.net up so you can view content on the page? I guess not, and thats where the problem is. Its not accessible on the internet for some reason.

soroccoheaven · 09-14-2007, 12:59 PM

when did you registered ? ..it takes 72-90 hours or so to populate ..so wait. and you can have a look on your dns status at www.dnsreport.com

soroccoheaven · 09-14-2007, 01:02 PM

[root@serv root]# ping born2explore.net
PING born2explore.net (84.215.5.246) 56(84) bytes of data.

--- born2explore.net ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 14999ms

[root@serv root]#

(it is resolving!! )but i can not ping your ip (may be disabled ) so see the firewall setting..

hondo · 09-14-2007, 02:34 PM

The domain was registered for about four days ago, so it cant be that. Yes, its resolving but cant ping the IP..thats a little weird i think and i dont understand why it cant ping the IP when it can resolve the domain.

I have uninstalled iptables/ipchains and there shouldnt be any firewall that is blocking the services or the ports. Port 53 was blocked by the router but has been opened for some hours ago now and nothing has changed except that i can see that port 53 is open as well as other needed ports. Thanks for the link.

soroccoheaven · 09-14-2007, 03:24 PM

check for port 80 i think its filtered too..

hondo · 09-14-2007, 03:54 PM

I have opend port 80, 53, 953, 22 etc. (the necessary ports i need).

soroccoheaven · 09-15-2007, 05:38 AM

can you pls. verify again ..

andyccn · 09-15-2007, 05:38 AM

What router are you using? Does it NAT the public IP address to an internal IP address?

Port 53 is definitely open and working, as like you say, you can resolve the domain.
Port 80 is definitely blocked somewhere along the way - is this hosted on an ADSL or other residential connection, cause some providers do block port 80 and 25 to prevent you running web/mail servers at home.

Try changing your webserver to listen on a completely random port - 3380 is a good one I've found before. Then open that port in your router and try again. If that works, chances are it's your provider blocking port 80.

If this is a dedicated/co-located machine in a proper data-centre, or a dedicated line, ignore all of the above ;-)

Code:

[NetServe@hyden ~]$ telnet 84.215.5.246 80
Trying 84.215.5.246...
telnet: connect to address 84.215.5.246: Connection timed out

andyccn · 09-15-2007, 05:42 AM

Actually, after some investigation it looks like your provider do block port 80.

Quote:

IP: 84.215.5.246
Host: cm-84.215.5.246.chello.no
Country: Norway

See here: http://archives.neohapsis.com/archiv...3-q1/0688.html

Quote:

accually, the rotterdam area of chello ISP blocks port 80.
They started blocking that when code red 1 almost took their internal network down.
Which meanth for *nix users, that first came the flood of requests that came with code red, then their port 80 was suddenly unreachable.
So instead of warning non-patching users, they block all users.

hondo · 09-18-2007, 10:01 AM

Thanks for the replies

Im sitting on an ADSL line at my appartment. Hmm, i have now configured apache to run on port 8080, could you check if you can see the contents of www.born2explore.net:8080 ? If the contents of this site is visible to you (it should just say something like "test page"), then im wondering if you know of a way to run this webserver with port 8080 open and still be able to type www.born2explore.net and get to see the contents of the site. Now you have to add the port number in the end of the domain name which noone will know that they will have to do.

andyccn · 09-18-2007, 01:36 PM

Yep, can see the test page

The only way you can do this is to get a provider who will receive your website visitors on port 80 (your www record will point to their servers), and transfer the content to/from your server on port 8080 (so your server is still hosting the site.)

One that springs to mind is No-IP. Their "No-IP+" packages provide what's termed as "Port 80 redirection."
http://www.no-ip.com/services/manage..._features.html

Other dynamic DNS providers may do it too, and maybe cheaper, but No-IP are the only ones I've come across so far.

hondo · 09-22-2007, 12:45 PM

Thanks for the reply, it seems like a solution. But i think ive found another solution for this (which is free and can be done on my server).

I was thinking about rerouting requests that are comming in on port 80 to port 8080 by setting up a rule with IPtables saying that every incoming request on 8080 should be rerouted to port 80 which will be what apache is running on. Im wondering if this will work, but i guess the ISP will block the port before it gets rerouted.

soroccoheaven · 09-22-2007, 01:51 PM

hello,

Hond0 you never mentioned that you are on adsl and using static/dynamic IP. Am i right ..?..ok. pls .provide some info.
1.is this domain is registered ?
2. using static/Dynamic Ip ?.
3. you connection to net ?.
Is it like internet-adsl-switch-clients modem(modem only or router too) ?
4. you need to forward port 80 only.but because it is in use forward 8080 for web server.
5. check you ip-domainname and domainame-ip transalation by using nslookup and dig comamnd.
6. If you are on dynamic IP you need dynamic dns updte client sofware ..sometimes it is providedwith the dsl modem pls check your modem for somthing like DDNS.
nothing else needed for webserver ..if you are able to browse you should be able to run your webserver on dsl too.