It looks like in your named.conf file that you are not "allowing transfer" to any other dns servers. You have to have a list (at least one or two) other dns servers that your dns server talks to and sends updates to.
Here is what my "options" section of my named.conf looks like:
Code:
options {
directory "/var/named";
allow-transfer {
204.238.213.42;
207.154.100.70;
208.39.140.42;
64.56.37.246;
66.122.64.130;
63.194.102.177;
63.194.102.178;
216.218.194.216;
216.240.152.133;
66.93.166.10;
64.4.141.88;
64.81.69.188;
66.218.71.205;
216.109.116.20;
};
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
//query-source address * port 53;
};
Try and grab a few of those and see what happens.
There is also an issue with your zone entry in your named.conf file. You have:
Code:
zone "pascobulldogs.com.db" {
type master;
file "pascobulldogs.com.db";
};
When it should be:
Code:
zone "pascobulldogs.com" IN {
type master;
file "pascobulldogs.com.db";
};
Looks like you had the db filename as the zone name when this needs to be the domain name. I also added the "IN" which I do not believe is absolutely neccessary on all system but it is more standard across the board to have it.
I also see you port scanned your sytem and saw that TCP port 53 is open and listening, but make sure that UDP port 53 is also open and listening.
Make the changes I have suggested and increment your zone file's serial number and then restart the server:
Then look in "/var/log/messages" for any error messages. If it says it started and broadcasted the zone properly you should be up and running. Just remember, if the name does not resolve locally on your machine first, it never will remotely for the rest of us out here. If it does start to resolve locally but not remotely then you are likely to have firewall issues.
Let me know how it goes.
