?
Solved

DNS Issue Again

Posted on 2013-06-12
13
Medium Priority
?
317 Views
Last Modified: 2013-06-14
Greetings.  I have the proxy server at thissite.thisdomain.domain.  My proxy server resolves correctly internally with just having DNS set thissite.thisdomain.domain to the internal IP address.  However, it is not resolving correctly when I try to go to www.aspresolver.com.thissite.thisdomain.domain.  I thought putting in the wildcard *.thissite.thisdomain.domain would work, but that doesn't seem to solve the problem. I also tried to put in www.aspresolver.com, thus creating www.aspresolver.com.thissite.thisdomain.domain would work but that did not work either.  Can someone please help me understand what I am doing wrong?
0
Comment
Question by:aclaus225
  • 7
  • 6
13 Comments
 
LVL 81

Expert Comment

by:arnold
ID: 39243469
How do you want it to resolve?
The issue might not be DNS but the server to which you are pointing this record where the issue is.
nslookup www.aspresolver.com.thissite.thisdomain.domain
or
dig www.aspresolver.com.thissite.thisdomain.domain.

telnet www.aspresolver.com.thissite.thisdomain.domain 80
GET http://www.aspresolver.com.thissite.thisdomain.domain/ HTTP/1.0

See what response you get.

not sure what you are trying to do so this is the best set of examples I can provide.
0
 

Author Comment

by:aclaus225
ID: 39244998
This resolved correctly externally:
Non-authoritative answer:
Name:    www.aspresolver.com.ezproxy.wscal.edu
Address:  174.77.164.85

Meaning that external DNS knows where it is at.  
When I put that address into my address bar, though, it goes into search mode instead of going to the page.
0
 

Author Comment

by:aclaus225
ID: 39245012
Additionally:
Z:\>ping www.aspresolver.com.ezproxy.wscal.edu

Pinging www.aspresolver.com.ezproxy.wscal.edu [192.168.100.57] with 32 bytes of
data:
Reply from 192.168.100.57: bytes=32 time<1ms TTL=128
Reply from 192.168.100.57: bytes=32 time<1ms TTL=128
Reply from 192.168.100.57: bytes=32 time<1ms TTL=128
Reply from 192.168.100.57: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.57:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Would indicate that my internal DNS knows where to go.  I am not getting it to resolve in a web browser though.
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
LVL 81

Expert Comment

by:arnold
ID: 39245024
Check your web server configuration and see whether the requests when they arrive to the 192.168.100.57 80 are the same as when they are hitting the external WAN IP port 80.

Are you forwarding the external connections to the same IP/POrt on the internal as the one in the example above?
0
 

Author Comment

by:aclaus225
ID: 39245307
Arnold, yes, the external IP is mapped to that internal IP.
0
 
LVL 81

Expert Comment

by:arnold
ID: 39245681
Which port on the web server is the external IP pointing to versus the default web site your internal access is being directed to.
0
 

Author Comment

by:aclaus225
ID: 39247825
I would say that both are pointed at 443 since it is https.  How am I supposed to point it at a specific port for access?
0
 
LVL 81

Expert Comment

by:arnold
ID: 39248225
could you double check your web server configuration?
Do you have only one default web site?

What is the web site running on?
IIS, Apache?
Apache
httpd -D DUMP_VHOSTS

IIS do you only have a single default web site? or do you have multiple sites.

Double check based on the log entries which site is being accessed when the traffic is going from the outside versus from the inside.
0
 

Author Comment

by:aclaus225
ID: 39248426
Arnold, this is a proxy server called EZ-Proxy.  As far as I know it is not running on either IIS or Apache.  There are no other sites on that computer.
0
 
LVL 81

Expert Comment

by:arnold
ID: 39248608
The proxy is not the one serving the page. It has to resolve the hostname you want to access and has to be able to connect to wherever this URL is to retrieve the data.
0
 

Author Comment

by:aclaus225
ID: 39249044
Arnold,
I am not quite sure then on this answer.  Here is the link for EZ-Proxy initial set up:
http://www.oclc.org/support/services/ezproxy/documentation/download/install-win32.en.html
0
 
LVL 81

Accepted Solution

by:
arnold earned 2000 total points
ID: 39249106
The discussion in the document you provide does not mention the layered URL you reference.

Please clarify what and how it used to work and how it is not working now.
Double check the DNS settings on the system where this EZ-Proxy is setup.

The issue might also be the party to which this proxy is supposed to provide access locked you out.
0
 

Author Closing Comment

by:aclaus225
ID: 39249159
Arnold, when I went to test it again everything seemed to be working appropriately.
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Is your organization moving toward a cloud and mobile-first environment? In this transition, your IT department will encounter many challenges, such as navigating how to: Deploy new applications and services to a growing team Accommodate employee…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

598 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question