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

[flash22@xxxxxxx]

On Mon, 17 Dec 2001, Patrick wrote:
> 
> >> >Primary Serial_Number  =  2001121303
> >> >Secondary Serial_Number  = 2001120315
> 
> This query came about because my Country Domain Authority refuses to
> authorise the domain change - because the secondary hasn't updated...
> Though they tell me I'm at fault because my primary must be higher than my
> secondary (which in fact it is...) And my ISP doesn't know there is a
> problem on the secondary (that long week-end)... This is a fault on the
> secondary?

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

> Question: How does the Domain Authority query these servers to discover
> these numbers? Can I do the same?

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

$ nslookup
Default Server:  localhost
Address:  127.0.0.1

> set type=SOA
> cobalt.com
Server:  localhost
Address:  127.0.0.1

cobalt.com
        origin = ns1.cobalt.com
        mail addr = root.ns1.cobalt.com
        serial = 2001110400
        refresh = 10800 (3H)
        retry   = 3600 (1H)
        expire  = 604800 (1W)
        minimum ttl = 86400 (1D)
cobalt.com      nameserver = ns1.cobalt.com
cobalt.com      nameserver = ns2.cobalt.com
ns1.cobalt.com  internet address = 63.77.128.10
ns2.cobalt.com  internet address = 63.77.128.11

[Obviously , use your own domain name ;]

PS: You can *guarantee the serial number is greater by making changes to
the zone a zay later, regardless of the sequence count, but don't make
changes right before the DNIC looks, it can catch the servers during a
zone transfer and be confused...

Also,as lomg as you are going to the trouble, make *absolutly certain*
your nameservers match, the nic's that are picky about serials are also
the ones are are ultra picky about nameserver consistancy

gsh