Hi Ceri,
   I understand why you would suggest that I add an A record for
www.vickiandstacey.com in the zone and reverse files, but what remains
with me is wondering *why* all was well earlier this morning - that is:
I was able to resolve wwww.vickiandstacey.com, returning the external IP
addr.., *and* able to resolve other local machines on the private lan
(including Demon.vickiandstacey.com), returning local private IP
addresses for them.
Upon my return from work (feeling rather pleased with myself too) I
thought I'd like to see this again, but that's when I saw that I was now
unable to resolve www.vickiandstacey.com (other Internet hosts were fine
btw).

With respect to you suggestion though, presuming that I am supposed to
add the external IP address for Demon in the zone file, what then
becomes of Demon's *internal* address?

That is to say, running nslookup from another lan box I would like
Demon's 192.168..... address returned, but running nslookup on
www.vickiandstacey.com should return the *external address (which is
what I saw earlier this morning).

>From your e-mail advice last evening, I thought that the new set up I
would attempting to implement would have then involved enabling my local
boxes to use Demon to resolve local machine names, but for external
addresses, my nameserver set-up would be such that these queries would
then be passed to my ISP's NS's.

Have I still got this concept wrong?

Thanks for the encouraging words by the way, I do appreciate your
efforts.

Stacey

On Thu, 2002-10-17 at 18:59, Ceri Davies wrote:
> On Thu, Oct 17, 2002 at 06:25:41PM +0100, Stacey Roberts wrote:
> > Thanks Ceri,
> >       The reason why I shied away from renaming the domain for the
> > private network, is because I actually *host* www.vickiandstacey.com on
> > Demon.vickiandstacey.com, and I'm not certain as to how having changed
> > the FQDN for private hosts would affect the webserver.
> 
> Oh right, I see!
> 
> In that case you'll probably want to be adding an A record for www
> pretty sharpish!  That's the reason that it's failing to resolve.
> 
> Also, if you want mail working for [EMAIL PROTECTED], then also add
> some MX records.
> 
> > I do want to learn as much as I can for this set up, Ceri.., please be
> > patient with me:-)
> 
> No worries - don't get the impression that I'm losing patience, I'm not,
> though sometimes I am rather terse and that gets misinterpreted :)
> 
> Ceri
> -- 
> you can't see when light's so strong
> you can't see when light is gone
-- 
Stacey Roberts
B.Sc (HONS) Computer Science

Web: www.vickiandstacey.com

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to