Client having problems with DNS after YUM update

G

galacnet

Verified User
Joined
Jan 17, 2006
Messages
25
One of my clients did a yum update and then some of his DNS records was wiped out. Several of his domains' DNS records were missing when I checked.

After going through dnsreport I found that there was no SOA reply...
So manually reinserted the DNS records for each missing domain and then restarted named again. And still not reply...

Checked the zone files in /var/named and they are there.

After that I looked into the logs and this was what came up
Apr 11 00:00:36 server named: named shutdown succeeded
Apr 11 00:00:37 server named[7819]: starting BIND 9.2.4 -u named -t /var/named/chroot
Apr 11 00:00:37 server named[7819]: using 1 CPU
Apr 11 00:00:37 server named[7819]: loading configuration from '/etc/named.conf'
Apr 11 00:00:37 server named[7819]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 11 00:00:37 server named[7819]: listening on IPv4 interface eth0, 203.211.138.167#53
Apr 11 00:00:37 server named[7819]: listening on IPv4 interface eth0:0, 203.211.138.168#53
Apr 11 00:00:37 server named[7819]: command channel listening on 127.0.0.1#953
Apr 11 00:00:37 server named[7819]: zone 0.in-addr.arpa/IN: loaded serial 42
Apr 11 00:00:37 server named[7819]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Apr 11 00:00:37 server named[7819]: zone 255.in-addr.arpa/IN: loaded serial 42
Apr 11 00:00:37 server named[7819]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
Apr 11 00:00:37 server named[7819]: zone dragonwild.com/IN: loaded serial 2007012603
Apr 11 00:00:37 server named[7819]: zone server.dragonwild.com/IN: loaded serial 2007010500
Apr 11 00:00:37 server named[7819]: zone jeremystcyr.com/IN: loaded serial 2007010500
Apr 11 00:00:37 server named[7819]: zone localdomain/IN: loaded serial 42
Apr 11 00:00:37 server named[7819]: zone localhost/IN: loaded serial 42
Apr 11 00:00:37 server named[7819]: zone teamwolfpack.net/IN: loaded serial 2007010500
Apr 11 00:00:37 server named[7819]: zone teamwolfpack.org/IN: loaded serial 2007010600
Apr 11 00:00:37 server named[7819]: zone predzpalace.co.uk/IN: loaded serial 2007010601
Apr 11 00:00:37 server named[7819]: running
Apr 11 00:00:37 server named[7819]: zone jeremystcyr.com/IN: sending notifies (serial 2007010500)
Apr 11 00:00:37 server named[7819]: zone server.dragonwild.com/IN: sending notifies (serial 2007010500)
Apr 11 00:00:37 server named[7819]: zone teamwolfpack.net/IN: sending notifies (serial 2007010500)
Apr 11 00:00:37 server named[7819]: zone predzpalace.co.uk/IN: sending notifies (serial 2007010601)
Apr 11 00:00:37 server named[7819]: zone dragonwild.com/IN: sending notifies (serial 2007012603)
Apr 11 00:00:37 server named[7819]: zone teamwolfpack.org/IN: sending notifies (serial 2007010600)
Apr 11 00:00:37 server named: named startup succeeded
Apr 11 00:13:02 server httpd: httpd shutdown succeeded
Click to expand...

Domains like www.dragonwild.com is working fine.
The ones manaually inserted like www.dragonslare.net fails to resolve...
Has been like this for almost 12 hours. usually it does not take that long to pick up...

Any ideas?

Thanks
 
Thanks for the pointers :)
How long does it usually take after restarting named to resolved?
 
Everything should start running again immediately.

Don't forget to exclude the package from future updates.

Jeff
 
humm... I didn't work so I backup the whole system and then reloaded all their backups for them and it started working again :)

What are the things I need to exclude from YUM? Incase there are other things other than bind that could screw up the system.

Wonder when will the admin level backups be ready :p much simplier to do it from the admin side than to load each reseller one by one.
 
The exclude line in yum needs to exclude any RPM that you've got installed that you don't want updated. To see what's intalled run:
Code: 
# rpm -qa
and check the resulting output.

Jeff
 
You must log in or register to reply here.
Back
Top