GreenLake Administration
Operating System - HP-UX
1844029
Members
2280
Online
110226
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
12-18-2008 05:03 AM
12-18-2008 05:03 AM
nslookup
i am new to DNS world.
I am having a DNS server. If i do
nslookup devteam.com
it is resolving to 67.23.45.76
I want to change this to some other ip. How can i do this. Where are these configurations.?
Points !!!!
regards
gV
I am having a DNS server. If i do
nslookup devteam.com
it is resolving to 67.23.45.76
I want to change this to some other ip. How can i do this. Where are these configurations.?
Points !!!!
regards
gV
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2008 05:40 AM
12-18-2008 05:40 AM
Re: nslookup
> I am having a DNS server...
What version?
The config file is in /etc/named.boot or /etc/named.conf depending on the version of BIND you have.
The DNS maps are usually in /etc/named/data.
What version?
The config file is in /etc/named.boot or /etc/named.conf depending on the version of BIND you have.
The DNS maps are usually in /etc/named/data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2008 05:43 AM
12-18-2008 05:43 AM
Re: nslookup
You did not mention your HP-UX version, which would allow us to identify the BIND DNS server version it probably uses.
Nevertheless, look into /etc/named.conf: this is the main configuration file in versions of BIND used in most modern HP-UX versions. This file will determine the DNS data directory and the names of the zone files within that directory.
In older versions of HP-UX, the name of the main configuration file might be /etc/named.boot. If so, the configuration syntax will be different from the current versions; it also means that the BIND version used is *ancient* and you should update it if at all possible.
See also the file /etc/rc.config.d/namesvrs and the NAMED_ARGS variable in that file: that file lists the parameters used in starting the name server daemon.
The process has the name "named" for legacy reasons: the actual current name of the DNS server software is BIND.
DNS data updates are done on the master server of the domain you're changing. The DNS zone data files contain a serial number: it is used to verify that the slave servers have the correct version of the data. When making any changes to a DNS zone file, you should always update the serial number of the zone file: otherwise your changes won't be propagated to the slave DNS servers of your zone.
In the DNS world, the mapping from the name devteam.com to IP address 67.23.45.76 is completely separate from the reverse mapping (IP 67.23.45.76 -> name devteam.com).
When changing an existing name to point to a new IP address, you should normally make changes to two separate DNS zone files: one in the regular zone file that maps the name to the IP, and another to the "reverse" zone file that maps the IP address back to the name.
Forgetting to change the second one is a common DNS mistake. It may cause problems in email delivery and validating SSL certificates.
MK
Nevertheless, look into /etc/named.conf: this is the main configuration file in versions of BIND used in most modern HP-UX versions. This file will determine the DNS data directory and the names of the zone files within that directory.
In older versions of HP-UX, the name of the main configuration file might be /etc/named.boot. If so, the configuration syntax will be different from the current versions; it also means that the BIND version used is *ancient* and you should update it if at all possible.
See also the file /etc/rc.config.d/namesvrs and the NAMED_ARGS variable in that file: that file lists the parameters used in starting the name server daemon.
The process has the name "named" for legacy reasons: the actual current name of the DNS server software is BIND.
DNS data updates are done on the master server of the domain you're changing. The DNS zone data files contain a serial number: it is used to verify that the slave servers have the correct version of the data. When making any changes to a DNS zone file, you should always update the serial number of the zone file: otherwise your changes won't be propagated to the slave DNS servers of your zone.
In the DNS world, the mapping from the name devteam.com to IP address 67.23.45.76 is completely separate from the reverse mapping (IP 67.23.45.76 -> name devteam.com).
When changing an existing name to point to a new IP address, you should normally make changes to two separate DNS zone files: one in the regular zone file that maps the name to the IP, and another to the "reverse" zone file that maps the IP address back to the name.
Forgetting to change the second one is a common DNS mistake. It may cause problems in email delivery and validating SSL certificates.
MK
MK
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