• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 326
  • Last Modified:

DNS will not work from inside the network...

We have a service with a company that is accessed with the address webapp.domain.com and it works perfectly when accesed from the external network. But when im trying to access it from the internal network it will not show the website give a page not found. Please help i restarted the server and i was able to access the website for a bit then it went away again.  When i ping the address from the internal network it seems to be pointing at this random ip which i have no idea where it came from.
0
Osram34
Asked:
Osram34
  • 6
  • 3
1 Solution
 
SommerblinkCommented:
Is the domain.com portion of the URL the same as your internal AD Domain?

If so, then you need to add an A record for that FQDN to your AD-DNS and point it to the IP address that it is supposed to go.


As far as the random address it resolves to, I have seen this specifically with domains purchased from Network Solutions, who will respond back with one of their IP addresses for a FQDN which doesn’t explicitly match AND you do not have any DNS suffixes listed in your DNS settings for your network card.

The test for this is when you ping the FQDN, you need to ping “webapp.domain.com.” Place the last dot there which will indicate to your DNS client that this is indeed the full and complete name.
0
 
SommerblinkCommented:
Err. Sorry, had that backwards regarding the dns suffixes... WITH a DNS suffix, which lists your AD-Domain name, which also happens to be a valid INTERNET domain name, then you can get unsuspecting results from your DNS client. Example.

You type in "www.google.com". Your DNS client will first try to resolve www.google.com. If this doesn't resolve, then it will go down your DNS suffix list, next trying to www.google.com.domainsuffix.com.

If domainsuffix.com happens to also be your domain on the internet, AND your DNS provider for domainsuffix.com has a wildcard entry, then it could resolve to someplace unexpected.
0
 
Osram34Author Commented:
the domain.com is not owned by us and is not the same as the internal AD domian... but i call them up and they say its an internal issue.  It wiered that when i jun nslookup from internal network seems like it pointing to a 206.344. ip instead of the 192.168 ip
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
SommerblinkCommented:
What happens when you try to resolve it with the trailing period at the end of the FQDN?

Also, don't use ping. Use nslookup. Ping may or may not query DNS for resolution. Nslookup always will.

Also, what about your hosts file?
0
 
Osram34Author Commented:
now when i do nslookup sub.domain.com. it shows my dns server/ad controller then it shows sub.domian.com with the right ip  address but when i try to access from my webserver it still shows no page found.
0
 
Osram34Author Commented:
When nslookup for jo.capsure.com. is done internaly it points to the ip address of simply capsure.com.... when nslookup of jo.capsure.com is done externally it point to the correct external ip address of my server.  These domains are actually with network solutions and i believe they did something to their configurations but since its a sub domain that pertains to me i dont have access to that account.  Earlier the nslookup done internal would give me the right ip for like 30 minutes then it would go back to point to the capsure.com ip address. Hostfiles have not been edited... nothing changed the system was working in the morning and went out on its own no server actually went down or anything...?????
0
 
PapertripCommented:
Assuming that is the actual name you are trying to resolve and not an example,

The authoritative nameservers for capsure.com do not have any records for jo.capsure.com.
[root@broken ~]# dig ns capsure.com +short
ns1.clt.peak-10.com.
ns1.jax.peak-10.com.

Open in new window

[root@broken ~]# dig @ns1.jax.peak-10.com jo.capsure.com

; <<>> DiG 9.7.0-P2-RedHat-9.7.0-5.P2.el6_0.1 <<>> @ns1.jax.peak-10.com jo.capsure.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46541
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;jo.capsure.com.                IN  A

;; AUTHORITY SECTION:
capsure.com.          10800     IN  SOA ns1.clt.peak-10.com. support.peak10.com. 2011102507 28800 7200 604800 10800

Open in new window

[root@broken ~]# dig @ns1.clt.peak-10.com jo.capsure.com

; <<>> DiG 9.7.0-P2-RedHat-9.7.0-5.P2.el6_0.1 <<>> @ns1.clt.peak-10.com jo.capsure.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12128
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available
<snip>

Open in new window

0
 
Osram34Author Commented:
joalvarez.capsure.com - ive kept on messing with the internal dns and cant get it to go... i suddenly came back and started working but for a about half hour again then stoped working.
0
 
Osram34Author Commented:
name server took about 10 days to update with new ip information. Started working on its own again... as been up for 4 days no problems
0
 
Osram34Author Commented:
temporary solution: edit hosts file for clients which needed to access the website (pointing to internal ip)

Long term solution: waiting for the name server that your isp uses to get new ip info
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now