HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- DNS Slaive Problem in Linux 8.0
Operating System - Linux
1828786
Members
2775
Online
109985
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2003 10:24 AM
03-29-2003 10:24 AM
DNS Slaive Problem in Linux 8.0
I have set up two DNS servers on Red Hat Linux 8.0
1.The primary DNS server is able to resolve names and ping the addresses defined.
2.But the secondary DNS is not able to resolve any name.
3.Also the Desktops clients are not able to resolve any name when I give the Primary DNS server IP address.
Can any suggest some solution for this.
I ahve crosschecked the settings in /etc/named.conf, they look ok.
How to trnsfer this zone?
1.The primary DNS server is able to resolve names and ping the addresses defined.
2.But the secondary DNS is not able to resolve any name.
3.Also the Desktops clients are not able to resolve any name when I give the Primary DNS server IP address.
Can any suggest some solution for this.
I ahve crosschecked the settings in /etc/named.conf, they look ok.
How to trnsfer this zone?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2003 10:58 AM
03-29-2003 10:58 AM
Re: DNS Slaive Problem in Linux 8.0
Note: The Slave must be authorized to receive the transfer from the Master DNS:
Zone transfer: Where the slave sends the master a NOTIFY request for a particular zone and the master responds with the information, if the slave is authorized to receive the transfer.
Here is the Red Hat How-To Link:
A mechanism called zone-transfer is used to copy the data. The zone transfer is controlled by your SOA record:
--------------------------------------------------------------------------------
@ IN SOA ns.linux.bogus. hostmaster.linux.bogus. (
199802151 ; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ) ; minimum, seconds
--------------------------------------------------------------------------------
A zone is only transferred if the serial number on the master is larger than on the slave. Every refresh interval the slave will check if the master has been updated. If the check fails (because the master is unavailable) it will retry the check every retry interval. If it continues to fail as long as the expire interval the slave will remove the zone from it's filesystem and no longer be a server for it.
http://www.europe.redhat.com/documentation/HOWTO/DNS-HOWTO-5.php3
SOA Recored:
http://www.europe.redhat.com/documentation/HOWTO/DNS-HOWTO-7.php3
Zone transfer: Where the slave sends the master a NOTIFY request for a particular zone and the master responds with the information, if the slave is authorized to receive the transfer.
Here is the Red Hat How-To Link:
A mechanism called zone-transfer is used to copy the data. The zone transfer is controlled by your SOA record:
--------------------------------------------------------------------------------
@ IN SOA ns.linux.bogus. hostmaster.linux.bogus. (
199802151 ; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ) ; minimum, seconds
--------------------------------------------------------------------------------
A zone is only transferred if the serial number on the master is larger than on the slave. Every refresh interval the slave will check if the master has been updated. If the check fails (because the master is unavailable) it will retry the check every retry interval. If it continues to fail as long as the expire interval the slave will remove the zone from it's filesystem and no longer be a server for it.
http://www.europe.redhat.com/documentation/HOWTO/DNS-HOWTO-5.php3
SOA Recored:
http://www.europe.redhat.com/documentation/HOWTO/DNS-HOWTO-7.php3
Support Fatherhood - Stop Family Law
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP