Sponsored Content
Operating Systems Solaris BIND DNS Server issue on Solaris 10 Post 302574690 by pludi on Friday 18th of November 2011 04:23:55 AM
Old 11-18-2011
You'll have to change the line
Code:
IN  NS     ns1.domain2.TLD.ccTLD. ; in the domain

to
Code:
domain2.TLD.ccTLD. IN  NS     ns1.domain2.TLD.ccTLD. ; in the domain

Besides, defining mail.domain1.TLD.ccTLD. as a CNAME for itself is quite strange.
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

2. Solaris

solaris - BIND / DNS

hi all forgive my ignorance, but when IVe set up DNS Ive put in the various server details in the /etc/resolv.conf and away I go. Suddenly Ive been reading about DNS, and I need to created a /etc/named.conf file. so, my question is this. DNS, what part does the /etc/resolv.conf play in... (3 Replies)
Discussion started by: sbk1972
3 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

Freebsd Bind DNS server - multiple subnets

Hello all, I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Discussion started by: kreno
0 Replies

5. Solaris

DNS Bind Upgradation in Solaris 10

Hi All , My current Bind version is BIND 9.6.1 and I want upgrade the same to BIND 9.8.1-P1 ,Can any one provide the steps to do the same ? Solaris Version : 5.10 Generic_144488-11 sun4v sparc Thanks , (0 Replies)
Discussion started by: sandeep.tk
0 Replies

6. Solaris

DNS server /var/spool issue

Hello all Currently I am working in a live production environment with 100+ Solaris servers . The environment has one DNS server and one SMTP server. The problem that I am facing since the past 2 months is that the /var/spool/mqueue on my DNS server keeps getting full i.e. mails with name... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies

7. UNIX for Dummies Questions & Answers

DNS server - /etc/resolv.conf file issue

Hi, Am trying to configure DNS server and trying to keep the information in /etc/resolv.conf file as: search server nameserver 192.168.0.10 when i restart the network service with #service network restart, resolv.conf file is changing as: nameserver 192.168.0.10 search server -... (5 Replies)
Discussion started by: raosr020
5 Replies

8. Ubuntu

Bind dns server zone file

I have a couple of zone conf files for the BIND server. There are some records that contains the "IN" statement and some do not. But anyway this works. So my question is what this "IN" is intended for? Here is the zone file example: ORIGIN . $ttl 60 example.com. IN SOA ... (4 Replies)
Discussion started by: andriesh
4 Replies

9. Solaris

How to add new Solaris client IP into Solaris 10 DNS server?

Hi, We just built a new Solaris 10 zone. And would like to add it to our DNS server. Its also Solaris 10. Please let me know how can I get the IP resolved using this DNS server. I added entry into zone config file but not working. I did restarted the DNS services. And also added nameserver name... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
lwresd(1M)																lwresd(1M)

NAME
lwresd - lightweight resolver daemon SYNOPSIS
config-file] debuglevel] pid-file] ncpus] query-port] port] directory] user-id] DESCRIPTION
The daemon provides name lookup services for clients that use the BIND 9 lightweight resolver library. It is essentially a stripped-down, caching-only name server that answers queries using the BIND 9 lightweight resolver protocol rather than the DNS protocol. listens for resolver queries on a UDP port on the IPv4 loopback interface, 127.0.0.1. This means that can only be used by processes run- ning on the local machine. By default, UDP port number 921 is used for lightweight resolver requests and responses. Incoming lightweight resolver requests are decoded by which then resolves them using the DNS protocol. When the DNS lookup completes, encodes the answers from the name servers in the lightweight resolver format and returns them to the client that made the original request. If the configuration file contains any entries, sends recursive DNS queries to those servers. This is similar to the use of forwarders in a caching name server. If no entries are present, or if forwarding fails, resolves the queries autonomously starting at the root name servers, using a compiled-in list of root-server hints. Options Use config-file as the configuration file. The default is Set the debug level to debuglevel. Debugging traces from become more verbose as the debug level increases. Run in the foreground. Run in the foreground and force all logging to standard error. Write the daemon's process ID to pid-file. The default is Create ncpus worker threads to take advantage of multiple CPUs. By default, tries to determine the number of CPUs present and creates one thread per CPU. If it cannot determine the number of CPUs, it creates a single worker thread. Send DNS lookups to port number query-port when querying name servers. This provides a way of testing the lightweight resolver daemon with a name server that listens for queries on a nonstandard port number. Listen for lightweight resolver queries on the loopback interface using UDP port number port. The default is port 921. Write memory usage statistics to standard output on exit. This option is only of interest to BIND 9 developers and may be removed or changed in a future release. Change root to directory immediately after reading the configuration file (see chroot(2)). Run as user-id, which is a user name or numeric ID that must be present in the password file. changes its user-id after it has carried out any privileged operations, such as writing the process-ID file or binding a socket to a privileged port (typically any port less than 1024). Note is a daemon for lightweight resolvers, not a lightweight daemon for resolvers. AUTHOR
was developed by the Internet Systems Consortium (ISC). FILES
Default resolver configuration file Default process-id file SEE ALSO
named(1M), chroot(2). available online at available from the Internet Systems Consortium at BIND 9.3 lwresd(1M)
All times are GMT -4. The time now is 08:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy