we have a hosted web site www.abc.com with DNS records maintained by the hosting company to rout mx, mail, smtp, and ftp.
I had to change their ftp dns entry to point to our new internally(dmz) ftp server we decided to hos ourselves. (ftp.abc.com)
I created a forward lookup zone on our DNS server abc.com with the FTP record to point to the ftp server in the dmz using the (vlan internal Ip). After that I wound having to added records for mail and smtp in order to ensure our users were able to route to the hosted IP/servers still. They had stopped working once I added the the abc.com zone internally.
Question www.abc.com works fine, but I can not nslookup "abc.com" successfully it no longer pingable or resolving with nslookup. How/can I resolve that for my 'internal' usrs. Note that externally all is fine, b/c external users are not using our DNS server, but rather the webhosting companies DNS records.
Please help with some suggestions/direction on what to consider next.