TomR said:
I have a client that is experiencing a few problems that have me puzzled.
I have configured the DNS server to point to the ISP DNS IP addresses. All
clients point to the server ip address 192.168.0.100. The name of teh Dns
server is say, servername.companyname.com. The web site is
www.companyname.com. All clients can get n the internet and send/receive
email. But, they can not go to their own web site,
www.companyname.com. If
I go to the command prompt to do nslookup and type
www.mycompany.com ... it
says "unknown, can't find
www.mycompany.com: non-existent domain." If I
type
www.mycompany.com in my browser outside the network, I go right to
their web site. I assume therefore it must be a DNS configuration ... any
thoughts/ideas?
You message above is pretty difficult to read but it sounds like a
problem common to those who are either new to Win2000+ or
who don't understand DNS (or both).
You need all Windows clients configured to ONLY resolve
names through internal name servers, e.g., DNS. They must
reliabley resolve internal names.
If you use the same zone name internally and exteranlly for
your Domain and outside DNS name then you must duplicate
the external zone internally -- it's called "shadow DNS."
This means you have an external DNS server (set) with a
primary and an INTERNAL DNS server set with a primary
or equivalent.
Since DNS Primaries will never replicate with each other
you must define all EXTERNAL resources TWICE: once on
the external and again on the internal DNS zone.
Internally, you can add additional records -- and use dynamic
DNS -- without worrying about private records migrating to
the outside.
Also, make sure to configure the internal DNS servers and
DCs as internal clients too -- only internal DNS on their
NIC configuration too.