I am having a problem with my name server. I am using it as its own name server and it works fine.

Though if I try to use it as my name server on a different PC it doesn't work. Nor can I ping my host
name.

I am behind a firewall, which is forwarding port 53 to this server. Also the PC in which I was using to
see if I could use this system as the DNS server is behind the firewall as well.

I am looking for any suggestions to get this address up and running.

Thank you in advance.

The domain name is registered at domains.com, and they have the ns1 and ns2 names as the name servers.

my configuration is printed out below.

Thank You


[root@localhost ~]# more /var/named/chroot/etc/named.conf
options {
directory "/var/named";
};

zone "." IN {
type hint;
file "named.root";
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
};

zone "yourdatamanagementsystems.com" IN {
type master;
file "yourdatamanagementsystems.hosts";
notify yes;
};

zone "119.64.in-addr-arpa" {
type master;
file "119.64.reverse";
notify yes;
};


[root@localhost ~]# more /var/named/chroot/var/named/named.root
; This file holds the information on root name servers needed to
; initialize cache of Internet domain name servers
; (e.g. reference this file in the "cache . <file>"
; configuration file of BIND domain name servers).
;
; This file is made available by InterNIC
; under anonymous FTP as
; file /domain/named.root
; on server FTP.INTERNIC.NET
; -OR- RS.INTERNIC.NET
;
; last update: Feb 04, 2008
; related version of root zone: 2008020400
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:BA3E::2:30
;
; formerly NS1.ISI.EDU
;
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 192.228.79.201
;
; formerly C.PSI.NET
;
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
;
; formerly TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
;
; formerly NS.NASA.GOV
;
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
;
; formerly NS.ISC.ORG
;
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
F.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:2f::f
;
; formerly NS.NIC.DDN.MIL
;
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
H.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:1::803f:235
;
; formerly NIC.NORDU.NET
;
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
;
; operated by VeriSign, Inc.
;
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30
J.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:C27::2:30
;
; operated by RIPE NCC
;
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
K.ROOT-SERVERS.NET. 3600000 AAAA 2001:7fd::1
;
; operated by ICANN
;
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 199.7.83.42
;
; operated by WIDE
;
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
M.ROOT-SERVERS.NET. 3600000 AAAA 2001:dc3::35
; End of File


[root@localhost ~]# more /var/named/chroot/var/named/named.local
@ IN SOA localhost. root.localhost. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum

IN NS localhost.

1 IN PTR localhost.


[root@localhost ~]# more /var/named/chroot/var/named/yourdatamanagementsystems.hosts
$TTL 1w
@ IN SOA pcks.yourdatamanagementsystems.com. dave.yourdatamanamgementsyst
ems.com. (
2002030601 ; Serial
21600 ; Refresh
1800 ; Retry
604800 ; Expire
900 ) ; Negative cache TTL



IN NS pcks.yourdatamanagementsystems.com

localhost IN A 127.0.0.1
pcks IN A 64.119.52.3
www IN CNAME pcks.yourdatamanagementsystems.com.
ns1 IN CNAME pcks.yourdatamanagementsystems.com.
ns2 IN CNAME pcks.yourdatamanagementsystems.com.


[root@localhost ~]# more /var/named/chroot/var/named/119.64.reverse
$TTL 1w

@ IN SOA pcks.yourdatamanagementsystems.com. dave.yourdatamanagementsyste
ms.com. (
1999022702 ; Serial
21600 ; Refresh
1800 ; Retry
604800 ; Expire
900 ) ; Negative chach TTL

IN NS pcks.yourdatamanagementsystems.com.

3.52 IN PTR pcks.yourdatamanagementsystems.com.

Is your named listening globally or just to local requests?

When diagnosing these kinds of things a good general technique is to use something like:

netstat -vlt

That will show you tcp ports that are listening.

If it's listening only on localhost:53 (localhost:dns), then you know
you need to edit your named.conf and add a "listen-on" option to open
the port up globally.

is the firewall forwarding both tcp and udp traffic?

i.e. nslookup in windows uses UDP

cjcox when you told me to look at my netstats it made me realize that I am forwarding to my server. I however, did NOT config my iptables to open port 53!!! I now have both firewalls forwarding and accepting port 53 on UDP and TCP.

I am still having trouble though. When I use my DNS server as my name server for my workstation I can ping it. Though when I use my ISPs name server as my name server I can't ping it anymore from my workstation.

Also, my IP address is 64.119.53.3 if that helps check my configuration.

My netstats command doesn't show my listening on port 53. It is as follows.

[root@localhost ~]# netstat -vlt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:netbios-ssn *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 192.168.1.103:domain *:* LISTEN
tcp 0 0 192.168.122.1:domain *:* LISTEN
tcp 0 0 localhost.localdomain:ipp *:* LISTEN
tcp 0 0 localhost.localdomain:rndc *:* LISTEN
tcp 0 0 *:microsoft-ds *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost6.localdomain:rndc *:* LISTEN

Well.. I'm glad my "advice" at least made you notice that even if my advice wasn't the issue at all!!

More info please. Are you pinging by name? Pinging inside or outside of the network?

Also, since you indicate that you might be running a firewall appliance of some kind, have you considered disabling the software firewall on the Linux host while you troubleshoot this... and then you can reenable it later. At least then you know you have a working config, the rest is just sw firewall configuration.

I am pinging to host named.

I know now that the software firewall isn't the problem because when I use the name server as the DNS server from my workstation is now works properly. Only after opening port 53 though...

In other words my name server works to resolve host names, but no other DNS server is realizing that this name server is used for that IP address it.

not responding

thats not accurate, let's take a look at these lines:
the ":domain" part means it's listening on 53, and i assume these are all your interfaces (running xen, are we?)
to make other name servers "realise you exist" you must verify with your domain company that they have an updated "glue" record of your name servers!

in other words, they need to have your dns server's ip address (A record) on their servers, so they can refer other dns servers to you!

make sure u have installed all the dependent rpm's also....

uninstall current version of DNS and reinstall it using all dependencies.

I already put in the request to register my name server and IP address with my domain company. I resubmitted it, and it is now working fine. Thank you all for the help.

It always seems that when ever I have problems it isn't with my configuration. It is always everything around Linux that is wrong.

I love this OS.

thanks again everyone