#1
  1. cave painting, the 1st Opn Src
    Devshed Novice (500 - 999 posts)

    Join Date
    Jun 2003
    Posts
    532
    Rep Power
    0

    DNS Error with Dynamic IP


    I have successfully setup Apache as a webserver on my LAN.
    I have a dynamic IP for my DSL so I got an acct at NO-IP.com for this.

    I can get to my webpage internally{LAN} with my No-Ip address or with http://localhost and with http://[Current ip address]

    I CANNOT see the web page from the INTERNET, I get a DNS ERROR Server Not Found...

    The Router is set to allow port 80 and port 85 for incomming requests.

    Is this an APACHE setting error or a DNS error or a routing issue?

    Most of my searches have been WAN can see server and LAN cannot. Someone has to have experienced this before, where Local is OK and Internet is fubar'd.

    Any links, suggestions for resolution appreciated..



    Toad
  2. #2
  3. DNS/BIND Guru
    Devshed Specialist (4000 - 4499 posts)

    Join Date
    Jun 2003
    Location
    OH, USA
    Posts
    4,266
    Rep Power
    173
    Need more info so that we can diagnose the problem:

    What is your current public IP
    What is the domain that should resolve to this IP

    I also use no-ip although my IP doesn't change very often.
  4. #3
  5. cave painting, the 1st Opn Src
    Devshed Novice (500 - 999 posts)

    Join Date
    Jun 2003
    Posts
    532
    Rep Power
    0

    follow-up


    current IP: 151.201.12.170
    No-IP name: rocbox.zapto.org

    I have tried this from a couple of different systems and always get a DNS ERROR when trying to connect.

    Did you setup the Virtual Host or Firewall on the ROUTER to move packets from no-ip thru to your server ??
    Last edited by dba_frog; June 23rd, 2003 at 11:55 AM.
  6. #4
  7. DNS/BIND Guru
    Devshed Specialist (4000 - 4499 posts)

    Join Date
    Jun 2003
    Location
    OH, USA
    Posts
    4,266
    Rep Power
    173
    DNS works fine:

    'ANY' Record Query

    'A' Record Query

    I then tried to connect to your browser. Then I tried telnet. Results:

    Connection attempts are timing out. If it was a connection refused error, then the router may be forwarding the connection, but your server isn't listening. However, since it is a connection attempt timed out, then most likely your router is ignoring the connection attempt.

    Solution:

    Properly forward TCP port 80 to the correct LAN IP.
    Last edited by SilentRage; June 28th, 2004 at 09:02 AM.
    Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links:

    Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts
  8. #5
  9. cave painting, the 1st Opn Src
    Devshed Novice (500 - 999 posts)

    Join Date
    Jun 2003
    Posts
    532
    Rep Power
    0
    Thanks for the diagnostic...

    Question, I didn't set up a VirtualHost and ServerName in the httpd.conf file. I read the documentation to say that if i DIDN'T set these then ALL request to the server would be handled by the default localhost path.

    But, now I am wondering...If the connection is live, but the server isn't responding, Do I need to define a VirtualHost? and NameServer?

    Wondering out loud...Toad
  10. #6
  11. DNS/BIND Guru
    Devshed Specialist (4000 - 4499 posts)

    Join Date
    Jun 2003
    Location
    OH, USA
    Posts
    4,266
    Rep Power
    173
    As I said, this has nothing to do with the server. I can't even connect to it. I don't even get a connection refused message. It just times out. That is most likely a router issue - or a personal firewall if you have one running.

    As for servername... set one. As for virtual hosts, go ahead and leave them alone.

IMN logo majestic logo threadwatch logo seochat tools logo