DNS and IIS

DNS and IIS (Full Version)

All Forums >> [Web Development] >> Server Issues

Message

stevie -> DNS and IIS (11/16/2004 15:16:03)
Okay I am running Three windows 2003 machines. Machine 1 is my webserver running IIS. Machine two and three are Dns servers. I cannot get my IIS server to answer outside traffic. It will resolve internally but not from outside. I have went to my registar, and registered my name servers. These servers point to the public IP's of my DNS servers. I sit behind a Cisco Pix, that has been setup by the Local provider and am assured that the correct ports are open. I pretty sure that it is DNS, cause I don't know anything about it. Can someone please point me in the right direction. I have read several articles, and many post, and just do not get it. Thanks!

Giomanach -> RE: DNS and IIS (11/16/2004 15:44:25)
My understanding has been that the Nameserver(s) are generally the same machine that holds the web... I mean, when using IIS locally, you have to use http://localhost or http://computername dependant on set-up, the DNS is controlled by the local machine... If anyone knows different, please, enlighten me

stevie -> RE: DNS and IIS (11/16/2004 15:54:48)
So I go to the registar, and set my name servers to go to the same public IP as my website? Do I even need to run DNS? Thanks for the reply!

aaronwiles -> RE: DNS and IIS (11/16/2004 18:42:39)
quote: ORIGINAL: Giomanach My understanding has been that the Nameserver(s) are generally the same machine that holds the web... I mean, when using IIS locally, you have to use http://localhost or http://computername dependant on set-up, the DNS is controlled by the local machine... If anyone knows different, please, enlighten me DNS server can be either the same machine or another machine, this normally depends on how big the network is and on the number of users. http://localhost or http://computername or web server ip address, all three will work.

aaronwiles -> RE: DNS and IIS (11/16/2004 19:01:14)
Are you using active directory? Can u access other web sites using your DNS servers internally. Firstly check that you are using your DNS servers & not a dynamically assigned one then try accessing a site that you have not visited b4 to check your DNS servers are resolving the domain to ip from outside. It is probably best, make that easiest to ensure that your DNS servers are resolving outside ip addresses first. If all works then try pinging your DNS server from outside & see if you get a response. Now I'm confusing myself, it's so much eaiser to do it yourslef that explain to others..... CAN I ASK.... Why are you using a DNS server? Do you actually need to? How many users on your network if any? Are you just using the web server for the web site externally?

stevie -> RE: DNS and IIS (11/16/2004 19:42:45)
Active directory yes. The DNS server does access outside sites, using itself. I am unable to ping because the Cisco Pix has disabled this function. The reason I am using DNS is I am required to by the head of the IS department. I'm not sure I understand nameservers completely. I did do a query on dnsreport.com. Here are the results. PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion. INFO NS records at parent servers Your NS records at the parent servers are: ns.grandcrowneresorts.com. [69.151.87.6] [TTL=172800] [US] ns.grandcrownetravelnetwork.com. [69.151.87.4] [TTL=172800] [US] [These were obtained from d.gtld-servers.net] PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there, with 2 entries. PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names. NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled. . You can see the results if you go to dnsreport.com and use bransondiscountpackages.com Thanks!

Giomanach -> RE: DNS and IIS (11/17/2004 7:36:58)
quote: I am unable to ping because the Cisco Pix has disabled this function. I do believe that the quote above is your problem....

stevie -> RE: DNS and IIS (11/17/2004 13:40:47)
Dan you where correct. It was the router. Thanks to all!!

stevie -> RE: DNS and IIS (11/17/2004 13:40:48)
Dan you where correct. It was the router. Thanks to all!!

stevie -> RE: DNS and IIS (11/17/2004 13:40:48)
Dan you where correct. It was the router. Thanks to all!!

stevie -> RE: DNS and IIS (11/17/2004 13:40:48)
Dan you where correct. It was the router. Thanks to all!!

Giomanach -> RE: DNS and IIS (11/17/2004 14:51:24)
One thank you is enough[;)]

aaronwiles -> RE: DNS and IIS (11/17/2004 18:36:27)
Dan you where correct. It was the router. Thanks to all!! [:D] LOL

aelias -> RE: DNS and IIS (12/27/2005 16:13:18)
I have to same exact problem except I can ping my server fine, ping is enabled on my firewall.

Universal4 -> RE: DNS and IIS (1/7/2006 14:33:52)
If your web server is behind a firewall running NAT, be sure the host headers for the sites are set to answer on the private IP's. Rick Universal4

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.0625