My DNS Server Is Lame

The messages in my logs indicate that my DNS server is configured incorrectly.

lame server resolving 'pobrdesign.com' (in 'pobrdesign.com'?): 209.40.198.107#53
lame server resolving 'pobrdesign.com' (in 'pobrdesign.com'?): 209.40.197.108#53

Here is a complete log from restarting named:

Code:
shutting down
stopping command channel on 127.0.0.1#953
no longer listening on 127.0.0.1#53
no longer listening on 209.40.198.107#53
no longer listening on 209.40.197.108#53
exiting
zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
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/localhost_resolver: loaded serial 1997022700
zone localdomain/IN/localhost_resolver: loaded serial 42
zone localhost/IN/localhost_resolver: loaded serial 42
zone pobrdesign.com/IN/external: loaded serial 2007081405
zone pobrdesign.com/IN/external: sending notifies (serial 2007081405)
client 209.40.198.107#45926: view localhost_resolver: received notify for zone 'pobrdesign.com': not authoritative
running

I configured my server through WHM initially. Here is my named.conf

Code:
1 include "/etc/rndc.key";
2
3 controls {
4 inet 127.0.0.1 allow { localhost; } keys { "rndckey"; };
5 };
6
7
8 options
9 {
10 /* make named use port 53 for the source of all queries, to allow
11 * firewalls to block all ports except 53:
12 */
13 query-source port 53;
14
15 // Put files that named is allowed to write in the data/ directory:
16 directory "/var/named"; // the default
17 dump-file "data/cache_dump.db";
18 statistics-file "data/named_stats.txt";
19 memstatistics-file "data/named_mem_stats.txt";
20 };
21
22 logging
23 {
24 /* If you want to enable debugging, eg. using the 'rndc trace' command,
25 * named will try to write the 'named.run' file in the $directory (/var/named).
26 * By default, SELinux policy does not allow named to modify the /var/named directory,
27 * so put the default debug log file in data/ :
28 */
29 channel default_debug {
30 file "data/named.run";
31 severity dynamic;
32 };
33 };
34
35
36 // All BIND 9 zones are in a "view", which allow different zones to be served
37 // to different types of client addresses, and for options to be set for groups
38 // of zones.
39 //
40 // By default, if named.conf contains no "view" clauses, all zones are in the
41 // "default" view, which matches all clients.
42 //
43 // If named.conf contains any "view" clause, then all zones MUST be in a view;
44 // so it is recommended to start off using views to avoid having to restructure
45 // your configuration files in the future.
46
47 view "localhost_resolver"
48 {
49 /* This view sets up named to be a localhost resolver ( caching only nameserver ).
50 * If all you want is a caching-only nameserver, then you need only define this view:
51 */
52 match-clients { localhost; };
53 match-destinations { localhost; };
54 recursion yes;
55
56 zone "." IN {
57 type hint;
58 file "/var/named/named.ca";
59 };
60
61 /* these are zones that contain definitions for all the localhost
62 * names and addresses, as recommended in RFC1912 - these names should
63 * ONLY be served to localhost clients:
64 */
65 include "/var/named/named.rfc1912.zones";
66 };
67
68 view "internal"
69 {
70 /* This view will contain zones you want to serve only to "internal" clients
71 that connect via your directly attached LAN interfaces - "localnets" .
72 */
73 match-clients { localnets; };
74 match-destinations { localnets; };
75 recursion yes;
76
77 zone "." IN {
78 type hint;
79 file "/var/named/named.ca";
80 };
81
82 // include "/var/named/named.rfc1912.zones";
83 // you should not serve your rfc1912 names to non-localhost clients.
84
85 // These are your "authoritative" internal zones, and would probably
86 // also be included in the "localhost_resolver" view above :
87 };
88
89 view "external"
90 {
91 /* This view will contain zones you want to serve only to "external" clients
92 * that have addresses that are not on your directly attached LAN interface subnets:
93 */
94 match-clients { !localnets; !localhost; };
95 match-destinations { !localnets; !localhost; };
96
97 recursion no;
98 // you'd probably want to deny recursion to external clients, so you don't
99 // end up providing free DNS service to all takers
100
101 // all views must contain the root hints zone:
102 zone "." IN {
103 type hint;
104 file "/var/named/named.ca";
105 };
106
107 // These are your "authoritative" external zones, and would probably
108 // contain entries for just your web and mail servers:
109
110 // BEGIN external zone entries
111
112 zone "pobrdesign.com" {
113 type master;
114 file "/var/named/pobrdesign.com.db";
115 };
116 };
Here is my /var/named/pobrdesign.com.db file:

Code:
; cPanel 11.6.0-BETA_15058
; Zone file for pobrdesign.com
$TTL 7200
@ 86400 IN SOA server.pobrdesign.com. support.pobrdesign.com. (
2007081405 ; serial, todays date+todays
86400 ; refresh, seconds
7200 ; retry, seconds
3600000 ; expire, seconds
86400 ) ; minimum, seconds

pobrdesign.com. 86400 IN NS server.pobrdesign.com.
pobrdesign.com. 86400 IN NS server2.pobrdesign.com.

pobrdesign.com. IN A 209.40.198.107

localhost.pobrdesign.com. IN A 127.0.0.1

mail IN CNAME pobrdesign.com.
www IN CNAME pobrdesign.com.
ftp IN A 209.40.198.107
pobrdesign.com. IN MX 1 ASPMX.L.GOOGLE.COM.
pobrdesign.com. IN MX 10 ASPMX5.GOOGLEMAIL.COM.
pobrdesign.com. IN MX 5 ALT1.ASPMX.L.GOOGLE.COM.
pobrdesign.com. IN MX 6 ALT2.ASPMX.L.GOOGLE.COM.
pobrdesign.com. IN MX 11 ASPMX4.GOOGLEMAIL.COM.
pobrdesign.com. IN MX 12 ASPMX3.GOOGLEMAIL.COM.
pobrdesign.com. IN MX 13 ASPMX2.GOOGLEMAIL.COM.
server 14400 IN A 209.40.197.108
server2 14400 IN A 209.40.198.107

glaring issue that is keeping my DNS from working.