|
-
Jun 28th, 2006, 06:02 AM
#1
Thread Starter
Fanatic Member
RE: DNS problem with Windows Sever Enterprise 2003
Hi all,
i have a bit of an issue with the DNS on Windows server 2003 Enterprise edition.
Right then this the issue.
Were starting to host our own company websites on our own server network. It's not a cluster domain and is managed by Active Directory, the sites have been created in IIS but nothing has been done in the DNS or Active Directory to this efect.
Now, we have purchased a domain name through a provider, and configured the TLD to point to our DNS, and forwards all queries to the ip address and the appropriate port, whch has worked and can be recognised to all computers that are a member of the domain, ore at least ahve privelages to access the domain.
The problems is that any public access machine, such as those connected to the internet wantign to visit the site, cant access it, its nt finding the ip addrss or the name server for external visitors. Also, the domain name is different to the DNS name.
Eg
www.name.co.uk
WebServer.another-name.com
Have looked at th si for the past couple of days and i'm not having any joys at all.
see what you guys think of this.
ether reply to my or grab me on MSN.
kaihirst AT hotmail.co.uk
ta
Kai
As the information I give is useful in its nature, consider using the RATE POST feature located on the bottom left of this post please..
A few things that make a good Developer a Great One.
 Methodical and a thorough approach to research and design inevitably leads to success.
Forward thinking is the key to Flow of control.
Never test in the design environment, always test in real time, you get the REAL results.
CBSE & OOSE are the same animal, they just require different techniques, and thinking.
SEO is a globe of objectives, SE rankings is an end to a means for these objectives, not part of them.
The key to good design is explicit attention to both detail and response.
Think Freely out of the "Box" you're in..... You will soar to better heights.
Kai Hirst - MSCE, MCDBA, MCSD, MCP, MCAP, MSCT
-
Jun 29th, 2006, 04:11 PM
#2
Re: DNS problem with Windows Sever Enterprise 2003
Did you setup a reverse lookup in DNS?
TPM
Add yourself to the VBForums Frappr Map!!
-
Jun 29th, 2006, 05:10 PM
#3
Re: DNS problem with Windows Sever Enterprise 2003
I'm assuming that you didn't overlook anything trivial, like your server being visible from outside your router? (IOW, from the internet?)
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
-
Jun 30th, 2006, 02:07 AM
#4
Thread Starter
Fanatic Member
Re: DNS problem with Windows Sever Enterprise 2003
Hi,
That is the actual problem.
Checked it out with dnsstuff and it cant resolove the ip address or the name lookup. I used a dynamic ip address and static ip address and a name loopkup with dyndns.com and the public ip address is different to the private ip address.
now i assume that this is somehting to do with terouter and not the server.
so the question lies is, how do I make the private ip address that is relevant to all the ports on the server and the sites active in IIS public, and recignised to the internet?
ive tried port forwrding, and this aint having none of it, and have tried using the primary gatewaay and the default gateway with the loopback adaptor, and this again is not playing at all.
Any ideas??
Ta
Kai
As the information I give is useful in its nature, consider using the RATE POST feature located on the bottom left of this post please..
A few things that make a good Developer a Great One.
Methodical and a thorough approach to research and design inevitably leads to success.
Forward thinking is the key to Flow of control.
Never test in the design environment, always test in real time, you get the REAL results.
CBSE & OOSE are the same animal, they just require different techniques, and thinking.
SEO is a globe of objectives, SE rankings is an end to a means for these objectives, not part of them.
The key to good design is explicit attention to both detail and response.
Think Freely out of the "Box" you're in..... You will soar to better heights.
Kai Hirst - MSCE, MCDBA, MCSD, MCP, MCAP, MSCT
-
Jun 30th, 2006, 02:35 AM
#5
Thread Starter
Fanatic Member
Re: DNS problem with Windows Sever Enterprise 2003
Hi,
Reverse loopkup with root hints have been setup BTW.
ta
kai
As the information I give is useful in its nature, consider using the RATE POST feature located on the bottom left of this post please..
A few things that make a good Developer a Great One.
Methodical and a thorough approach to research and design inevitably leads to success.
Forward thinking is the key to Flow of control.
Never test in the design environment, always test in real time, you get the REAL results.
CBSE & OOSE are the same animal, they just require different techniques, and thinking.
SEO is a globe of objectives, SE rankings is an end to a means for these objectives, not part of them.
The key to good design is explicit attention to both detail and response.
Think Freely out of the "Box" you're in..... You will soar to better heights.
Kai Hirst - MSCE, MCDBA, MCSD, MCP, MCAP, MSCT
-
Jul 3rd, 2006, 02:20 PM
#6
Re: DNS problem with Windows Sever Enterprise 2003
 Originally Posted by kaihirst
ive tried port forwrding, and this aint having none of it
See my post in your other thread.
and have tried using the primary gatewaay and the default gateway
That gives people access to your router, which is what lives at the gateway address. Unless you have remote access enabled, it's a dead address from outside.
with the loopback adaptor
That's a kind of virtual device. All it means is that if you try to connect to your external address (once you set things up properly), the router knows to just connect you to the forwarded computer, rather than try to connect to something out there in the world. It only exists fron the LAN (the computers on your network), not the WAN (the world).
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote