 |  |
This is a good demonstration of why it's not good to manually
Re: Newbee Question
From: Men & Mice Support
Date: Friday, March 16, 2001
Time: 2:29:08 pm
configure the zone data on your "secondary" server. You have two
master servers and a lame delegation, and the two master servers have
different data.
Here's the delegation from com (taken from f.gtld-servers.net):
snakefeet.com. NS stiinc.com.
snakefeet.com. NS toaster.snakefeet.com.
snakefeet.com. NS ducky.snakefeet.com.
stiinc.com. A 64.123.3.99
toaster.snakefeet.com. A 64.123.3.98
ducky.snakefeet.com. A 209.198.141.180
The first two listed servers are authoritative for the zone, but the
third is not.
Of the two authoritative servers, when asked for records named
crouse.snakefeet.com, they give the following answers:
from 64.123.3.98:
crouse.snakefeet.com. A 64.245.49.53
snakefeet.com. NS ns2.snakefeet.com.
snakefeet.com. NS ns1.snakefeet.com.
[Note: No A records for the two name server names.]
from 64.123.3.99:
The host or domain "crouse.snakefeet.com." does not exist
When asked for records for snakefeet.com, the second server gives
these records as part of the answer:
snakefeet.com. NS ns2.snakefeet.com.
snakefeet.com. NS ns1.snakefeet.com.
ns2.snakefeet.com. A 64.123.3.99
ns1.snakefeet.com. A 64.123.3.98
The solution has several steps:
1. Add the A records for ns1 and ns2 to 64.123.3.98.
2. Remove the master zone file from 64.123.3.99. Configure this
server as a slave server, so that it gets its data from the master
server. This fixes the inconsistency with crouse, as well.
3. Decide whether you want to use 209.198.141.180 as a server. If so,
configure it as a slave server. If not, remove it from the delegation
records.
4. Rename these servers in the delegation. This may be very
difficult. It's also not terribly important, except for stiinc.com -
you may at some future point wish to use that name elsewhere, and you
don't currently have an A record for it.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
At 11:21 AM -0600 3/16/01, Jay Menna wrote:
>I have had snakefeet.com running on QuickDNS for a year.
>
>I was using a few friends as secondary servers. They were all unix geeks.
>I'm not sure what they were running. I do not know the status of the
>secondary servers at this time.
>
>A few days ago I set up an a record for crouse.snakefeet.com. Half of the
>world was able to see it but lots of other people could not.
>
>So I got he name servers changed to new secondary servers (all QuickDNS)
>
>I set up the DNS on all the secondary servers manually. SO I could be sure
>it was there.
>
>Still some of the world could not see it. So I thought it must be stuck in
>a bunch of Cache files all over the place, Give it time and it will work
>itself out. It have been a week and it has not worked itself out.
>
>What is generally the problem when part of the world can resolve DNS and the
>other part can't? Is this my problem?
Messages In This Thread:
Return to Digital Point Solutions' Home Page