Fully Qualified Domain Name is what you get from the Domain Registrar. Typically the name you want with a .com/net/org/ blah blah.
That name means nothing on the internet until a Name Server is granted authoritative for the name and provides an address. The Registar inititally assigns their name servers as authoritative for the domain name. To have your own name servers be authoritative for your domain name, you must first register your name servers with the domain registar then assign them as authoritative for your name. Then create records which will resolve your name to your public IP address. That's for hosting your own web site with your own web servers on your own network using your publically assigned ISP address.
Now, if you have a 3rd party web hosting company host your web site, their address is used to point any query for your site to their servers. If you happen to also have your internal network use the same FQDN as your web site, your going to have a problem getting to your web site from inside your network. That's because your internal DNS servers will resolve the query for your domian name and not forward them to root hint servers on the internet. So, you'll never get to see your hosted site internally unless you know the actual address.
then you would have to type 10.0.0.0:80 in the address bar to see your web site. Remember, when you type in http://www.yourdomain.com what your really typing in is your address with the appropriate port #. [the example 10.0.0.0:80= http://www.yourdomain.com] That's all DNS does resolve a name to an address [forward lookup] or an address to a name [reverse lookup].
I'll have to look on Microsoft Help and Support site for a KB article which solves the problem of 3rd party web hosting for a FQDN with the same internal FQDN for a private network.
But that's the gist of your problem. Your users are asking for http://www.yourdomain.com and your internal DNS server will resolve that name to your server address because your internal network uses the same FQDN internall as externally. It will not fail to resolve therefore forward the failed query to internet root hint servers for resolution, therefore direct the query to the web hosting service hosting your web site.