- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- DNS problem update denied
Operating System - Linux
1753416
Members
6989
Online
108793
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
Discussions
Discussions
Forums
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
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
тАО06-26-2002 05:10 PM
тАО06-26-2002 05:10 PM
DNS problem update denied
Hi .
can you help me?
we have public and private networks here.
when I used to restart dns
then syslog is generated such logs
what is that? what is the logs?
entire private IP are normal but a few are abnormal
see attached file
can you help me?
we have public and private networks here.
when I used to restart dns
then syslog is generated such logs
what is that? what is the logs?
entire private IP are normal but a few are abnormal
see attached file
Step by step
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 10:31 AM
тАО06-27-2002 10:31 AM
Re: DNS problem update denied
Hello,
It seems that the servers with IP 190.168.1.213 and 190.168.1.245 try to update the reverse zone 1.168.190.in-addr.arpa.
Before BIND8, the only security between primary and secondary zones was IP iddress checking.
Starting with BIND8, zone transfers and updates betweek primary and master DNS servers can be made more secure using cryptographic keys.
Here, your DNS server is rejecting updates from the IP addresses found in the syslog.
If you want further explanations, please post your /etc/named.conf.
Good luck.
Kodjo
It seems that the servers with IP 190.168.1.213 and 190.168.1.245 try to update the reverse zone 1.168.190.in-addr.arpa.
Before BIND8, the only security between primary and secondary zones was IP iddress checking.
Starting with BIND8, zone transfers and updates betweek primary and master DNS servers can be made more secure using cryptographic keys.
Here, your DNS server is rejecting updates from the IP addresses found in the syslog.
If you want further explanations, please post your /etc/named.conf.
Good luck.
Kodjo
Learn and explain...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 05:53 PM
тАО06-27-2002 05:53 PM
Re: DNS problem update denied
Thanks Kodjo Agbenu
I will post named.conf and zone file
see attached file
I will post named.conf and zone file
see attached file
Step by step
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 06:04 PM
тАО06-27-2002 06:04 PM
Re: DNS problem update denied
my mistake
not 192.168.1.* but 190.168.1.*
thanks.
not 192.168.1.* but 190.168.1.*
thanks.
Step by step
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP