Local DNS and unresolvable virtual web host

Barry Margolin barmar at bbnplanet.com
Wed Sep 22 17:17:24 UTC 1999


In article <37E8B858.E5F2C848 at gatcombe.com>,
Chris P. Gatcombe <chris at gatcombe.com> wrote:
>Hi all,
>
>I run a home Windows network with a Linux firewall/gateway/router on
>which I run a nameserver. I also own a domain name "mydomain.com", with
>a virtual web host hosted by a third party provider. My internal windows
>PCs can't resolve the "www.mydomain.com" address of my virtual web host.
>I know it exists - I can access it from my work network, but nslookup
>fails to find it, even when I specify a specific nameserver to use.

>Is it that I'm telling my nameserver that I'm authoritative for
>mydomain.com and hence it will never look anywhere else for info?

Yes, that's what "authoritative" means -- it thinks it knows everything
there is to know about that zone.  You need to add an entry for that domain
to your named.mydomain.com file.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list