News: This forum is now permanently frozen.
Pages: [1]
Topic: Weird DNS related problem - Urgent Help/Suggestions pls  (Read 2193 times)
« on: May 23, 2008, 20:55:12 »
Gilrod *
Posts: 15

Hi all,
We're a small game dev company and have just installed Subversions on one of our boxes.

For some reason it can only be accessed externally to our offices (using the url http://svn.DOMAINNAME.com) the problem is internally if we try to connect with TortoiseSVN, or indeed anyother client it doesn't connect at all, doesn't even get to the login page.

On two of the machines I've tried using nslookup to make sure it's ok, however when I enter svn.DOMAINNAME.com instead of that returning, I get the following ...

Code:
Default Server:  m0n0wall.DOMAINNAME.com
Address:  192.168.7.1

> svn.DOMAINNAME.com
Server:  m0n0wall.DOMAINNAME.com
Address:  192.168.7.1

Non-authoritative answer:
Name:    svn.DOMAINNAME.com.DOMAINNAME.com
Address:  XX.YY.110.250

Any ideas? we've been trying to solve the issue since Tuesday, and all we come back to is an issue with m0n0wall...

The internal IP for the SVN box is 192.168.7.100

We've flushed dns on both machines, but still the same..

Help..

Cheers
« Reply #1 on: May 23, 2008, 21:23:13 »
Fred Grayson *****
Posts: 994

When you go to the m0n0wall page: Firewall: NAT: Inbound, do you not see the below at the bottom of the page?

Note:
It is not possible to access NATed services using the WAN IP address from within LAN (or an optional network).


--
Google is your friend and Bob's your uncle.
« Reply #2 on: May 23, 2008, 21:30:48 »
Gilrod *
Posts: 15

I do, but am not looking for a WAN IP....?!?

As I have the svn.DOMAINNAME.com registered in the DNS Forwarder to forward to 192.168.7.100 I would expect m0n0wall to get the internal request and opt for that IP...

« Reply #3 on: May 23, 2008, 21:53:54 »
Fred Grayson *****
Posts: 994

Is svn.DOMAINNAME.com your WAN IP or not? If it is then services NAT'd from that address to a LAN IP can not be reached from the LAN when using the WAN IP or a name that resolves to it.

You should have mentioned that you are using the forwarder. For the forwarder to work, you must be using m0n0wall's LAN IP as the only DNS server on your LAN machines. Are you?


--
Google is your friend and Bob's your uncle.
« Reply #4 on: May 23, 2008, 22:03:01 »
Gilrod *
Posts: 15

Your questions ...

*.DOMAINNAME.COM (apart from www.) all point to our servers here via a WAN IP.

Surely though LAN IP' override WAN IP' ? especially if being looked for on the LAN ?!

Yes we are ONLY using the m0n0wall DNS server, NO OTHERS.

« Last Edit: May 23, 2008, 23:56:59 by Gilrod »
« Reply #5 on: May 24, 2008, 02:20:01 »
ChainSaw
Guest

check your PM.

CS...
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines