DNS query for customer website
Hi all,
Having an issue with a couple of newly inherited networks that I look after and I'm a bit stumped.
They are SBS 2011 networks, with the internal DNS being "customer.com.au" rather than "customer.local".
It appears they've done this for Exchange, and as I've been out of the game for a while I'm stumped.
Seeing the mail server is no issue at all "mail.customer.com.au" however I can't for the life of me get onto their website, which is externally hosted. "http://www.customer.com.au"
I've had a look at forwarding but the default website seems to be grabbing my traffic.
Could you please help!!
Having an issue with a couple of newly inherited networks that I look after and I'm a bit stumped.
They are SBS 2011 networks, with the internal DNS being "customer.com.au" rather than "customer.local".
It appears they've done this for Exchange, and as I've been out of the game for a while I'm stumped.
Seeing the mail server is no issue at all "mail.customer.com.au" however I can't for the life of me get onto their website, which is externally hosted. "http://www.customer.com.au"
I've had a look at forwarding but the default website seems to be grabbing my traffic.
Could you please help!!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm not sure about other hosting companies, but with mine, I get an email when and if the IP is going to change....that's happened once since going with them.
So I wouldn't expect the website to change IPs very often.
So I wouldn't expect the website to change IPs very often.
Internally, the Domain Name Server holds the authoritative role on the Windows Domain customer.com.au and DNS will not look-up external references (forwarders) for domains which it holds.
Hopefully the provider of the web-site does not change the IP address of the "www" too often, for every time the IP address changes, the static entry in the internal DNS will have to be updated.
Bear in mind that with having to set DNS this way, if an internal user does not include "www" in the URL - it will still fail to reach the external web site.