[cobalt-users] Reverse DNS and Err/TO getting serial# messages

[Barbara - <thebizworkers@xxxxxxxxx>]

Can anyone possibly shed some light on what's going on
with my secondary DNS setup? I'm completely at a loss.

Last week I signed up for a second RaQ4 system from a
seperate provider from my first system. I now have two
systems, one on each side of the country, and I wanted
to setup the machines to correctly run primary and
secondary DNS for the domains that I host. It appears
that when I initially setup a domain with primary and
secondary DNS, all is fine. The trouble seems to start
after several days when the secondary records start to
expire then can't get the serial updated correctly,
and then fail. 

On my Primary DNS system after setting up a record I
see the following in the logs:

named: master zone "domain_A.tld" (IN) loaded (serial
0003202320)
named: approved AXFR from [SECONDARY-DNS-IP].1278 for
"domain_A.tld"
named: zone transfer (AXFR) of "domain_A.tld" (IN) to
[SECONDARY-DNS-IP].1278

named: master zone "domain_B.tld" (IN) loaded (serial
0003202320)
named: approved AXFR from [SECONDARY-DNS-IP].1278 for
"domain_B.tld"
named: zone transfer (AXFR) of "domain_B.tld" (IN) to
[SECONDARY-DNS-IP].1278

Then once I add a secondary record for the domains on
the Secondary system I see these messages in the logs:

named: rcvd NOTIFY(domain_A.tld, IN, SOA) from
[PRIMARY-DNS-IP].1220
named: rcvd NOTIFY(domain_B.tld, IN, SOA) from
[PRIMARY-DNS-IP].1220
named: rcvd NOTIFY(domain_C.tld, IN, SOA) from
[PRIMARY-DNS-IP].1220

It appears all the secondary records get
created/xfered correctly to/on the secondary system
under the /etc/named directory. 

But then several days later I start seeing this in the
logs off the secondary DNS system.

On Secondary DNS system:
-------------------------
named: Err/TO getting serial# for "domain_A.tld"
named: Err/TO getting serial# for "domain_B.tld"
named: Err/TO getting serial# for "domain_C.tld"

named-xfer: connect(PRIMARY-DNS-IP) for zone
domain_A.tld failed: No route to host
named-xfer: connect(PRIMARY-DNS-IP) for zone
domain_B.tld failed: No route to host
named-xfer: connect(PRIMARY-DNS-IP) for zone
domain_C.tld failed: No route to host

I'm wondering if this could be because neither colo
facility (that houses the RaQ's) seems to be allowing
Reverse DNS of my IP's. I've setup PTR records
correctly on the primary DNS system, but when trying
to perform a RDNS lookup on any of the IP's I get this
message:

PRIMARY-DNS-IP has badly configured reverse DNS.

The reverse DNS for PRIMARY-DNS-IP is unassigned, but
unassigned, doesn't resolve to anything.

-IF- I perform a reverse DNS lookup on the
SECONDARY-DNS-IP it's even worse:

SECONDARY-DNS-IP has no reverse DNS configured.

But both primary and secondary IP's *DO* have PTR
records on the primary machine... Could this be what's
causing the "No route to host" errors? If so, then how
in the world could someone actually run a secondary
DNS server if their colo facility doesn't delegate
RDNS to their machines? Or am I completely off base
here.  :-)

Any suggestions or ideas would be greatly appreciated.

Barbara

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com