Login or Register to Ask a Question and Join Our Community


IP Networking

lan DNS and telnet and GNS

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums IP Networking lan DNS and telnet and GNS
# 1  
Old 01-29-2010
lan DNS and telnet and GNS
hi

i am stuck middle of this configuration.plz help me outta it.
/../chroot/etc/named.conf
Code:
// Enterprise Linux BIND Configuration Tool
// 
// Default initial "Caching Only" name server configuration
//

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;
//directory "/var/named";
        allow-query { sayantan-chakraborty; };
        forwarders { 208.67.222.222; 208.67.220.220; }; # ISP primary/secondary
    //forward-only; # Rely completely on ISP for cache misses
};

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

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

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

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

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 {
        type master;
    file "named.ip6.local";
    allow-update { none; };
};

zone "255.in-addr.arpa." IN {
    type master;
    file "named.broadcast";
    allow-update { none; };
};

zone "0.in-addr.arpa." IN {
    type master;
    file "named.zero";
    allow-update { none; };
};

include "/etc/rndc.key";

# Forward Zone for sayantan.chakraborty domain
zone "sayantan.chakraborty" IN {
        type master;
        file "sayantan.chakraborty.zone";
};

# Reverse Zone for sayantan.chakraborty domain
zone "1.168.192.in-addr.arpa" IN {
        type master;
        file "192.168.1.zone";            
};

acl sayantan-chakraborty { 192.168.1.0/24; 127.0/8; };
//options {
        
//};

/.../chroot/var/named/192.168.1.zone
Code:
$TTL 1D

@       IN      SOA     rac-1.sayantan.chakraborty foo.bar.tld. (
200612060       ; serial
2H              ; refresh slaves
5M              ; retry
1W              ; expire
1M              ; Negative TTL
)

        IN      NS      rac-1.sayantan.chakraborty
2      IN      PTR      rac-1.sayantan.chakraborty
1       IN      PTR     router.sayantan.chakraborty
3       IN      PTR     rac-2.sayantan.chakraborty

/.../chroot/sayantan.chakraborty.zone

Code:
$TTL 1D

sayantan.chakraborty.             IN      SOA     rac-1.sayantan.chakraborty. foo.bar.tld. (
                                200612060                 ; serial
                                2H                        ; refresh slaves
                                5M                        ; retry
                                1W                        ; expire
                                1M                        ; Negative TTL
                                )

@                       IN      NS      rac-1.sayantan.chakraborty.

rac-1.sayantan.chakraborty.       IN      A       192.168.1.2      ; RHEL server
router.sayantan.chakraborty.      IN      A       192.168.1.1      ; router
rac-2.sayantan.chakraborty.       IN      A       192.168.1.3      ; OEL slave

                              ; aliases
www            IN    CNAME    rac-1.sayantan.chakraborty. ; WWW server    
virtual            IN    CNAME    rac-1             ; virtual WWW tests
mail                    IN      CNAME   rac-1    ; sendmail host

                              ; DHCP Clients
dhcp01.sayantan.chakraborty      IN      A       192.168.1.100
dhcp02.sayantan.chakraborty      IN      A       192.168.1.101
dhcp03.sayantan.chakraborty      IN      A       192.168.1.102
dhcp04.sayantan.chakraborty      IN      A       192.168.1.103
dhcp05.sayantan.chakraborty      IN      A       192.168.1.104

@                       IN      MX  10  mail.sayantan.chakraborty

but for dig result no answer section is found.:

Code:
[root@rac-1 var]# dig rac-1.sayantan.chakraborty.

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> rac-1.sayantan.chakraborty.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60831
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;rac-1.sayantan.chakraborty.    IN      A

;; AUTHORITY SECTION:
.                       7622    IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2010012900 1800 900 604800 86400

;; Query time: 37 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jan 29 18:50:10 2010
;; MSG SIZE  rcvd: 119

[root@rac-1 var]#

my /named.root
Code:
; root "." zone hints file, queried of a.root-servers.net. by system-config-bind
; version of root zone: 2009122100
.            518400    IN    NS    D.ROOT-SERVERS.NET.
.            518400    IN    NS    M.ROOT-SERVERS.NET.
.            518400    IN    NS    J.ROOT-SERVERS.NET.
.            518400    IN    NS    E.ROOT-SERVERS.NET.
.            518400    IN    NS    L.ROOT-SERVERS.NET.
.            518400    IN    NS    H.ROOT-SERVERS.NET.
.            518400    IN    NS    K.ROOT-SERVERS.NET.
.            518400    IN    NS    B.ROOT-SERVERS.NET.
.            518400    IN    NS    A.ROOT-SERVERS.NET.
.            518400    IN    NS    G.ROOT-SERVERS.NET.
.            518400    IN    NS    C.ROOT-SERVERS.NET.
.            518400    IN    NS    I.ROOT-SERVERS.NET.
.            518400    IN    NS    F.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET.    3600000    IN    A    198.41.0.4
A.ROOT-SERVERS.NET.    3600000    IN    AAAA    2001:503:ba3e::2:30
B.ROOT-SERVERS.NET.    3600000    IN    A    192.228.79.201
C.ROOT-SERVERS.NET.    3600000    IN    A    192.33.4.12
D.ROOT-SERVERS.NET.    3600000    IN    A    128.8.10.90
E.ROOT-SERVERS.NET.    3600000    IN    A    192.203.230.10
F.ROOT-SERVERS.NET.    3600000    IN    A    192.5.5.241
F.ROOT-SERVERS.NET.    3600000    IN    AAAA    2001:500:2f::f
G.ROOT-SERVERS.NET.    3600000    IN    A    192.112.36.4
H.ROOT-SERVERS.NET.    3600000    IN    A    128.63.2.53
H.ROOT-SERVERS.NET.    3600000    IN    AAAA    2001:500:1::803f:235
I.ROOT-SERVERS.NET.    3600000    IN    A    192.36.148.17
J.ROOT-SERVERS.NET.    3600000    IN    A    192.58.128.30
J.ROOT-SERVERS.NET.    3600000    IN    AAAA    2001:503:c27::2:30

Code:
[root@rac-1 var]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:00:E8:F7:02:B0  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e8ff:fef7:2b0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10604 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11862 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6864690 (6.5 MiB)  TX bytes:2683554 (2.5 MiB)
          Interrupt:177 Base address:0x8400 

eth1      Link encap:Ethernet  HWaddr 00:26:18:59:EE:49  
          inet addr:192.168.181.10  Bcast:192.168.181.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:fe9c0000-fea00000 

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:2117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4323804 (4.1 MiB)  TX bytes:4323804 (4.1 MiB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:9648 (9.4 KiB)

[root@rac-1 var]# 
[root@rac-1 ~]# service named status
number of zones: 8
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/1000
tcp clients: 0/100
server is up and running
named (pid  5976) is running...
[root@rac-1 ~]#

1)how to solve it?
2)and how to make this DNS to aware of DHCP.
3)where to specify the other nics?i have a private network connection.
Last edited by csayantan; 01-29-2010 at 09:36 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

2. Red Hat

Different hostnames with reboot while lan cable, no lan cable

I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable Reboot with lan cable: The hostname is ubunut Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies

3. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

4. IP Networking

Local Lan, no-ip directed DNS forward, surf within lan

Hi, We have a website running on a local centos 5.4 surfer, static IP. The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server. My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine. However, we cannot see... (3 Replies)
Discussion started by: lawstudent
3 Replies

5. IP Networking

LAN server - Proxy, DNS, WEB - I'm lost!!!

Ok! I started to do something and I got lost...and crazy! I got MW2000S gateway device that provides wireless internet access! It is configured to work as NAT. Clients connect to MW and have access to internet and it works beautifully! And now! In the same network I have Ubuntu machine. First I... (0 Replies)
Discussion started by: salvor_hardin
0 Replies

6. IP Networking

DNS on LAN

Hi all. I am trying to use BIND9 as DNS server. All goes well, except that i can't lookup my relative LAN hostnames instead of full domain names. F.e. i can lookup host hostname.subdomain.domain but can't host hostname This is my master zone file --------------------- $TTL 3h... (2 Replies)
Discussion started by: kukuruku
2 Replies

7. Solaris

How to configure private LAN and coporate LAN on the same machine-Solaris10

Hi , I am trying to configure a private LAN and corporate LAN on the same machien on Solaris 10. How can I achieve this? Thanks (1 Reply)
Discussion started by: deedee
1 Replies

8. UNIX for Advanced & Expert Users

disabiling telnet and ftp from reversing DNS

Hello Everybody: Im facing a weird problem over here. Eventhough my UNIX servers (sol9& tru64) are stand alone servers, and they dont see or use the DNS server, but recently after crash in our DNS and replacing it with new one and new IP, when I try to telnet or FTP some of these servers from... (1 Reply)
Discussion started by: aladdin
1 Replies

9. UNIX for Dummies Questions & Answers

telnet refused / reverse DNS issue?

I have users with laptops who may telnet from the local network one minute and then connect remotely a short time later from a different IP address. This causes a problem as the UnixWare 7.1.1 server appears to try to resolve the remote machine name (via our primary DNS server) to the IP... (4 Replies)
Discussion started by: rm -r *
4 Replies
Login or Register to Ask a Question