Ok here's the setup
CISCO Router thats running NAT for our network
2 WINNT DNS Servers running SP6.a
One DNS is multihomed (internal NATted IP and external public IP) and is our external DNS. The internal IP points to the internal DNS and the external IP is pointed to itself for DNS
The internal DNS has only one IP and its NATted and points to itself for DNS
Both host\lmhost files on the servers are blank
Problem is.. We seem to have people be unable to access out internal IIS web server. But it seems geogrpahical in nature
The west coast (up to Texas) can access the Web Server no probs..the East coast cannot access and gets various different types of errors (from timeouts, page cannot be accessed..etc)
Took my test PC outside the router and did an nslookup. I made the external DNS my nameserver and lookup my web server and it spat out the NATted IP address when it should have given me the Public IP which is an A record in my table.
Still using nslookup, I made another DNS I know (east coast) my nameserver. This DNS is an NS record in both my external and internal DNS servers
It also gave me the NATted IP address for the webserver instead of the public.
Checked the lmhost/host files on my test machine and they are blank and the DNS is pointing to the external DNS server in its network configuration.
So why am I getting NATted IP addresses and why can only some people access my Web Server??
Thanks in advance
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You mentioned that the Internet address of the host is an A record in the DNS server. Is there also an A record for the private address of the host? It could be that if you have both of them, the server is handing out the two addresses in a round-robin method, so that half the queries are wrong. Also, are the internal users getting the wrong address sometimes too?
DNS has no concept of which address is closest or best for you when you are inside the LAN, or outside on the itnernet. As sugegsted if the server has two cards and two addresses then DNS assumes both are available to anyone who asks to resolve the address and will normally round-robin between them.
Its not a good idea to us the same DNS for internal and external use anyway but if for some reason you need or want to you could always add another A record for external users with a different name so that they get to the server from a different address. If you are resolving www.domain.com for instance then just remove the NATted address for this record from DNS and internal users will access it using the external card address.
The best way though is to keep one DNS server for internal and one for external. If you change to W2K or above you will need a huge amount of stuff in DNS and it /really/ isn't a good idea to give all that out to the hackers :-)
Steve
kcferret,
I don't think you are going to get any further with this unless you can run different DNS's as suggested before. Don't forget to close the question :-)
"How do I know what grade to give?":
http://www.experts-exchang
Steve
How did you get around the problem.
I have the same issue happening with me,
I have a DC wich is also a public DNS and its
advertising its Internal IP address!
I already built a new DC and no longer need
the DNS server to act as a DC.
Should I delete the (A)Host records from the DC zone?
There are NS records as well.
Any ideas are welcome.
Business Accounts
Answer for Membership
by: somchaiuPosted on 2002-12-06 at 03:07:02ID: 7541468
I think you should separate DNS for internal usage and public DNS server. The internal DNS can have only private address, while the public DNS server have only public address. Let the users from internet see only the resource record of public internet address.