I don't think so. I don't think you should have the same name twice in
your hosts file. I'm not sure off hand which address linux would return
in this case. (How would it know when to return which one?)
What makes this work is that one resolver (your local resolver) is used
when connected to
I am not sure I quite understand why it doesn't work and a resolver
is needed. If I do a dig it answers to the proper IP. It stands to
reason that I should be able to access that server through a web
browser, and it cannot. What is a resolver going to tell my system
On 05/21/2012 10:59 AM, Cecil Yother, Jr. wrote:
I am not sure I quite understand why it doesn't work and a resolver is
needed. If I do a dig it answers to the proper IP. It stands to reason
that I should be able to access that server through a web browser, and
it cannot. What is a resolver
On 05/21/2012 11:12 AM, Eric Shubert wrote:
On
05/21/2012 10:59 AM, Cecil Yother, Jr. wrote:
I am not sure I quite understand why it
doesn't work and a resolver is
needed. If I do a dig it answers to the proper IP. It stands
On 05/21/2012 11:14 AM, Cecil Yother, Jr. wrote:
On 05/21/2012 11:12 AM, Eric Shubert wrote:
On 05/21/2012 10:59 AM, Cecil Yother, Jr. wrote:
I am not sure I quite understand why it doesn't work and a resolver is
needed. If I do a dig it answers to the proper IP. It stands to reason
that I
On 05/21/2012 11:24 AM, Cecil Yother, Jr. wrote:
It resolves to the correct address, but will not answer. I just added
the LAN address, ie.
Listen 192.168.0.168:80
to the httpd.conf file and now it answers and I'm able to access the
pages, but it's not answering them via the WAN.
--
On 05/21/2012 11:46 AM, Eric Shubert wrote:
On
05/21/2012 11:24 AM, Cecil Yother, Jr. wrote:
It resolves to the correct address, but
will not answer. I just added
the LAN address, ie.
Listen
On 05/21/2012 11:59 AM, Cecil Yother, Jr. wrote:
On 05/21/2012 11:46 AM, Eric Shubert wrote:
On 05/21/2012 11:24 AM, Cecil Yother, Jr. wrote:
It resolves to the correct address, but will not answer. I just added
the LAN address, ie.
Listen 192.168.0.168:80
to the httpd.conf file and now
I've found the same thing. It appears that some network devices don't
let you do a u-turn, coming from the inside and returning to the inside.
I'm not sure which ones or why that is, but I'd like to know more about
it. BL, Deepen's solution works for me as well.
--
-Eric 'shubes'
On
On Friday 18 May 2012 09:53 PM, Eric Shubert wrote:
I've found the same thing. It appears that some network devices don't
let you do a u-turn, coming from the inside and returning to the
inside. I'm not sure which ones or why that is, but I'd like to know
more about it. BL, Deepen's solution
DearMaxwellyou can use ETHO ETH1 different ..provide you have two different network mask.Like I have Local Network Internet Network.Whats your requirement actually.
- Deepen Dhulla
“Nothing is particularly hard if you divide it into small jobs.”
http://in.linkedin.com/in/deependhulla
11 matches
Mail list logo
