the
client machine is still asking the ns1.my-isp.net nameserver.
So how can I rectify this issue then?
Thank you for your help.
MERRY CHRISTMAS TO ALL!!!
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [GnuDIP] PING problem with GNUDip updated hostnames
Date: Sat
]
To: [EMAIL PROTECTED]
Subject: Re: [GnuDIP] PING problem with GNUDip updated hostnames
Date: Sat, 20 Dec 2003 07:45:25 -0700
By the way, if you do not really require secondary DNS on someone
else's network, there is no reason that you have to do this.
Plan A:
Try using ns2.mydomain.com as your other
==
[prev in list] [next in list] [prev in thread] [next in thread]
List: gnudip2-general
Subject: Re: [GnuDIP] PING problem with GNUDip updated hostnames
From: gnudip2-general-admin () lists ! sourceforge ! net
Date: 2003
ISP, it will NEVER find my
hostname's A record.
How can I rectify this issue?
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [GnuDIP] PING problem with GNUDip updated hostnames
Date: Fri, 19 Dec 2003 10:34:44 +0800
Hi,
One issue that it might
IN A 200.100.10.50
This seems OK to me. But it's the ZONE File that I think looks sorta weird.
If I run 'dig mydomain.com. ns', the return is the exact same as the above.
Any clues???
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [GnuDIP] PING problem with GNUDip
