[cobalt-users] Re: DNS-network serial numbers?

[Patrick <rockdog@xxxxxxxxxxx>]

>It's part of the domain record, here's how to do it yourself
>
>$ nslookup

Flash22 - This went a long way towards answering my questions... Must admit -
didn't venture on to the command line... I used a tool - queried  my domain -
looks 100 percent.

>Maybe, maybe not, are you in fact notifying the secondary that you have
>zone changes? Is it listening?

If I could prompt the secondary it would be great... Surely the secondary sees
the update by default?

Related:
Jeff - 
>
> > Question: How does the Domain Authority query these servers to discover
> > these numbers? Can I do the same?
>
> If you haven't done that, how do you know what the serial is on the
> secondary?


I didn't know the serial on the secondary (or the primary when I started this.)
- The domain authority sent me the numbers - as something I should rectify...
But the problem is on the secondary(?) - I don't own the secondary.

I still don't know the actual number on the secondary - my lookup yielded:  
serial 2259699319 on my NS as the primary - At some point I did pull it all out
- and then rebuilt the SOA records from scratch... hence the high(er) serial
now (as compared to the original...)

>
> and then I wanted to get the serial number from ns2.ns-one.net, which is
> the secondary dns:


I will use your procedure to check the secondary. Knowing how to use tools
correctly helps. Thanks.

>
> If you're running DNS from the gui, when you commit changes, DNS will
> reload the zone file.  When you do it manually you have to restart or
> reload the DNS server as Gerald has showed you.


DNS will reload the zone file on the primary - and the secondary will see the
new zone file - and do its own zone transfer - from the primary to the
secondary(?)... 

>
> The Red Hat Bible


This sounds like a good choice... more specific.

Jeff - in a related post to Farooq - you wrote:

>
> 4. Find out from whoever gives you your connectivity whether or not
> they've delegated "reverse" DNS to you; if they have, set up ONE reverse
> DNS record for each IP# you've got, not one for each domain you're
> hosting.


I certainly set up PTR records for the host domain name. Does this have any
bearing on whether the secondary updates or not?

>
> Do you want us to do DNS for you <smile>?  We're not _that_ expensive
> <smile, again>???


More expensive than my isp. This was the point of the exercise though - me
doing it myself. Contacting the local coven is valid.

- Patrick.
PS. Gerald=flash22? :)