named giving me lot of trouble in centos 6.5
I'm working on migrating to a new server and named is giving me tons of issues:
1: At random, the /var/named/chroot/etc/named.conf file VANISHES! WTF? Typically this happens when it fails to load. Then I have to restore from backup. Why is it doing this? Also when I go to vim it from another folder it wants to create a directory. I have to cd to that folder to edit it (that's when it does not vanish). There seems to be a backup in /etc/ thankfully. Overall it's acting very messed up. 2: Every time I go to restart named, I get this error: Code:
umount: /var/named/chroot/var/named: device is busy. Code:
Filesystem Size Used Avail Use% Mounted on Overall this version of named seems really flaky. Is there a way to fix all of this? |
Another thing I just realized is it only works locally, it refuses to resolve anything from an external server.
Ex: if I use nslookup this is what I get: Code:
> server 192.99.10.155 #1: it keeps adding .loc after. No idea why. But even without that, it still does not work. This is the contents of /var/named/chroot/etc/named.conf: Code:
options { Mostly everything is default except for zone.conf file and the actual zone files which are verbatim from the working DNS server. I ensured to open up the DNS port in the firewall. |
It *seems* to work now, but I'll have to leave it alone overnight and see.
|
The output of mount gives me trouble. Specially cause the root file system seems to be mounted on the named working directory. I would say this is also the reason for the named.conf to disappear. Nother thing I can't get my head around is why the restart of named unmounts a filesystem?
How did you install named in the first place? |
Quote:
Another weird thing I noticed is there is another chroot folder within the /var/named/chroot/var/named folder. This is a mess. For all intent and purposes it seems to be working now though... but still find it weird how it's acting so differently than any other named installation I've seen. All those fake mount points are also kind of a pain in the ass. Seems like really dirty programming, whatever they're trying to accomplish with all this. |
ok I take that back, this version of named is flacky as hell. Suddenly it's not working anymore. I was right in the middle of transferring some of my domains to the new server then realized none of them work. This is a mess.
Just getting SURVFAIL left and right when I use nslookup and all my sites are down. Part of the issue might be that my new server provider does not provide more than 1 IP without having to order more and they're being slow at provisioning them so I have ns1 and ns2 pointed to the same IP, could that be an issue? edit: And now it works... Now I transffered everything over to the new nameserver so I think I need to stop touching it for a while and see what happens... I think this issue is a combination of my browser constantly wanting to cache stuff and my local DNS also caching stuff. If I use isup.me everything does work. |
I don't think that pointing the two ns record to the same IP would cause such a behaviour. Also its not the intended way to use nameservers it should be okay for the start. Just get a second server and point the other ns record this one. Two IP's on the same server don't bring redundence into your nameserver setup.
The install way seems valid for me. Also long time ago i fidled with rpm based distros. How do you restart the server? /etc/rc.d/named restart? or similar? If so check on the script and see if you find any mount commands inside. Which just should not be there in my opinion. Maybe you should see if you can setup a fresh machine at home and rebuild your server. If this works out well, maybe just reinstall the server with the new build image. At least you would know if all of thats what happening is "normal" behaviour. Which I doubt. |
This is a dedicated server that is online facing, so it cost a lot per month, not getting a second box. I don't really have the option to host from home (ISP wont allow it) otherwise I would be hosting everything from home, it would be much easier!
This is the entire init file for named: Code:
#!/bin/bash There does seem to be some mount stuff in there. No idea why named would need to mount anything or do anything having to do with the file system. |
All times are GMT -5. The time now is 10:08 PM. |