FQDN can't see itself

[jcasetnl]

We have a web server with local hostname 'hostweb'. It has a FQDN of 'webserver.ourdomain.com'. Our DNS reg is mapped to an external address assigned to our router, which is nat'd to 'hostweb's' internal address.

When you hit the site from the outside, everything is fine. But if you're actually on 'hostweb', and it tries to hit itself via its FQDN, it fails. Additionally, all internal clients in our network have the same problem. However, on 'hostweb', I can ping the FQDN without any problem.

Do I need to configure something in our reverse lookup zone on our Win 2k3 box?

 

[ITPangaeaArchitect]

the webserver.ourdomain.com record, I assume it is held on your registrar?

Internally, clients have to hit the internal IP, which means you will have to create a cname with the name webserver (if AD, it will add the ourdomain.com itself) pointing to the internal IP.

The external people are using the record on the registrar to get to your router, which then sends that port to the correct internal IP.

Am I understanding you correctly, is this your config? Or are you missing the internal part?

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[ITPangaeaArchitect]

anotehr way to check it (from a domain member who is a member of the same domain)...try using

http://hostweb

and see if you can get to it (this is of course assuming there is no :8085 type info in the actual web address)

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[jcasetnl]

Brandon,

I think you are correct. I need to add the cname to our Win2k3 server so that internal clients get routed to the internal IP.

I'll test that. Thanks!