Issue with a zone file

[david510]

Hello All,

I am fairly new to DA.

I am having issue with a domain. The domain is not digging at the server and outside. I checked for the zone file and it is there in the path /var/named/domain.com.db

When I checked from the DA DNS admin panel, I cannot see the domain.com listed in the DNS admin panel. It is listed in the "List domains" list. I tried recreating the dns zone after moving the zone file in the name /var/named/domain.com.db.bkp and restarting named. Then DA admin shows the zone already exists. What am I missing here?

Regards,
David

 

[chatwizrd]

Did you add the domain in /var/named/named.conf or whereever named.conf is then restart named?

 

[david510]

I have made sure there is no entry for the domain in the /etc/named.conf file. The default named.conf in DA wil be located at /etc directory right?

 

[chatwizrd]

Well it has to be in named.conf to be serving the domain name. It needs to be a line like:

zone "domain.net" { type master; file "/etc/namedb/domain.net.db"; };

Just copy how the other domain files look and add one with that domain. Then restart named with /sbin/service named restart.

 

[david510]

Thanks Chatwizard,

I was able to figure out the dns setup on DA For some reason, the zone file domain.com is not listed in those files and when I try to create it it says the dns entry already exists

Is there any other files I need to check.
Thanks for your help

Regards,
David

 

[chatwizrd]

I would just edit it via the shell to add the domain in /etc/named.conf

Use an editor like pico nano or via then restart named. Otherwise using directadmin you would have to delete the entire domain and readd it.

Usually that error means that its already in named.conf though.

 

[nobaloney]

It's possible for there to be two named.conf files on the server, one used by DA and one used by named.

It happens in some cases after an update to the named daemon, perhaps by an automated process.

What happens is the update creates a chrooted server where there wasn't one before.

The symptom is generally that newly added domains don't work but old ones do.

Try (from the command line as root):

# locate named.conf

and then check to see if the one in /etc is a pointer to the one in the chroot directory.

If not, then the fix depends on which one is "right".

Jeff

 

[david510]

Hi Jeff,

Hurray!!

Thanks for your trick. I was able to figure out the issue. As you said, there were different named files.

Thanks to Chatwizard also for helping me out.

Regards,
David