DNS Problem

[spa77]

Hello, I hope someone can help me with a big (!) DNS problem.

I have a Windows NT 4 Server which uses IIS to host many different web sites. On the server, I have DNS setup as a primary with my ISP providing the secondary DNS. The server had a fixed external IP address and everything was working fine .... until a move to broadband.

With this, our broadband router now has a different external IP address with our DNS/Web NT server having a fixed internal (192.168) address. People can now no longer get to any of our sites. We have changed the domain nameservers at our nominated registry, modified all DNS entries to point to the fixed internal address, reconfigured IIS to pick up requests for "unassigned" and added port forwarding for ports 80, 53 (both TCP and UDP) plus 25 and 110 on our router. Our ISP, who is our secondary DNS, says that their nameservers have been updated with the new external IP address. Browsers are still unable to get to the site though.

Traces to the IP address work fine, but not to the domain name. I'm stuck now. My ISP is being unhelpful and I have exhausted my knowledge of DNS! Can anyone help!?

Thanks.

 

[SgtB]

Does running an nslookup from the outside give you the correct IP address? I never use port forwarding on a router, so I'm not sure...does this work the same as standard NAT?
The only DNS server that really matters is the ISP's (IMO), if they have it set up, then people should be able to resolve your domain to IP.
In order to rule out DNS, let's do an nslookup from the outside (seperate dial-up connection maybe...or I'll do it for you if you want). Once that is done we can continue troubleshooting.

PS - Your DNS server should use your ISP's DNS as a forwarder, not a secondary site. ________________________________________
Check out

http://www.security-forums.com