We help IT Professionals succeed at work.
Get Started

CentOS server DNS

_3mp3ror_
_3mp3ror_ asked
on
1,048 Views
Last Modified: 2013-12-16
I am trying to figure out how to make a new server up and running for the first time.
I got it already installed with centos 5.5 64bit and xampp

the domain name is already bought, and on the server I have already a static ip address but I don't really quite know why I can't make the connection with name <=> ip.
here are my config files:

resolv.conf
---------------------------
webhosting company's nameserver

nameserver 5.6.7.8
nameserver 6.7.8.9

Open in new window



ifconfig
---------------------------

bond0     Link encap:Ethernet  HWaddr 
          inet addr:1.2.3.4  Bcast:1.2.3.255  Mask:255.255.255.0
          inet6 addr:  Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:139946968 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13486554 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:29338819024 (27.3 GiB)  TX bytes:18510804055 (17.2 GiB)

bond0:1   Link encap:Ethernet  HWaddr
          inet addr:1.2.3.5  Bcast:1.2.3.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

bond0:2   Link encap:Ethernet  HWaddr 
          inet addr:1.2.3.6  Bcast:1.2.3.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:82587831 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13486549 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:25495735389 (23.7 GiB)  TX bytes:18510803677 (17.2 GiB)
          Interrupt:169 Memory:da000000-da012800

eth1      Link encap:Ethernet  HWaddr
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:57359137 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3843083635 (3.5 GiB)  TX bytes:378 (378.0 b)
          Interrupt:225 Memory:dc000000-dc012800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10314 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10314 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:523463 (511.1 KiB)  TX bytes:523463 (511.1 KiB)

Open in new window


/etc/named.conf
---------------------------

//
// named.conf for Red Hat caching-nameserver
//

options {
   directory "/var/named";
   dump-file "/var/named/data/cache_dump.db";
   statistics-file "/var/named/data/named_stats.txt";
/*
 * 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;
};

//
// a caching only nameserver config
//
controls {
 inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

zone "localhost" IN {
   type master;
   file "localhost.zone";
   allow-update { none; };
};

zone "mydomainname.abc" IN {
   type master;
   file "/var/named/mydomainname.abc.zone";
   allow-update { none; };
};

zone "7.6.5.in-addr.arpa" IN {
   type master;
   file "/var/named/7.6.5.rev";
   allow-update { none; };
};

include "/etc/rndc.key";

Open in new window


var/named/7.6.5.rev
---------------------------

$TTL    86400
@       IN      SOA     mydomainname.abc. root.mydomainname.abc (
100     ; serial
1H      ; refresh
1M      ; retry
1W      ; expiry
1D)     ; minimum
@       IN      NS      ns1.mydomainname.abc.
1       IN      PTR     binggo.mydomainname.abc.

Open in new window


var/named/mydomainname.abc.zone
---------------------------

$TTL            86400
@       IN      SOA            mydomainname.abc.  root.mydomainname.abc. (
100                             ; serial
1H                              ; refresh
1M                              ; retry
1W                              ; expiry
1D )                            ; minimum
@       IN      NS             ns1.mydomainname.abc
@       IN      A                 5.6.7.8
ns1     IN      A                 5.6.7.8
@       IN      MX      10      mail.mydomainname.abc.
mail    IN      A                 5.6.7.8
WWW     IN      A                 5.6.7.8

Open in new window


When I do nslookup i get
nslookup mydomainname.abc
Server:         5.6.7.8
Address:       5.6.7.8#53

** server can't find mydomainname.abc: NXDOMAIN

Open in new window

and dig

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mydomainname.abc
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 28303
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
mydomainname.abc.                 IN      A

;; Query time: 8 msec
;; SERVER: 5.6.7.8#53(5.6.7.8)
;; WHEN: Tue Jun 15 19:43:08 2010
;; MSG SIZE  rcvd: 31

Open in new window


I am new to this kind of thing so explain to me why it's not working properly and what do I need to do to make it work.

Thanks.
Comment
Watch Question
Commented:
This problem has been solved!
Unlock 1 Answer and 13 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE