paleogryph
MIS
RH 6.2 running named. How do newly installed Linux boxes (static) on the network "get into" the name server records?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DNS question 1
- Thread starter paleogryph
- Start date
- Status
-
1
- #2
Hello,
I don't exactly understand your question. Can you explain a little more?
Are you asking about adding the new hosts' records on the named server or just "forcing" the new hosts to ask the dns server for IP-hostname resolution?
Bye,
jmiturbe
I don't exactly understand your question. Can you explain a little more?
Are you asking about adding the new hosts' records on the named server or just "forcing" the new hosts to ask the dns server for IP-hostname resolution?
Bye,
jmiturbe
- Thread starter
- #4
paleogryph
MIS
Yes, I'm trying to find out how to add the new hosts record to the dns box, so that others on the network can ping the new host via name by using dns.
I have the new linux box on the network with a static address. It knows who/where the dns is and it can ping anything else (and itself) by name and ip.
However, no other box can ping it by name, only ip.
On the new box in question I have /etc/resolv.conf as follows:
domain domain.com
search domain.com
nameserver xxx.xxx.xxx.xxx (our internal dns)
nameserver xxx.xxx.xxx.xxx (primary external dns)
nameserver xxx.xxx.xxx.xxx (secondary external dns)
Like I said, the box in question can ping anything via name. No one can ping it via name. I know I can add the box to anybodies host file, whether windows or linux and then they could see it, but I would like to understand how named "adds" newly introduced hosts.
thanks again
I have the new linux box on the network with a static address. It knows who/where the dns is and it can ping anything else (and itself) by name and ip.
However, no other box can ping it by name, only ip.
On the new box in question I have /etc/resolv.conf as follows:
domain domain.com
search domain.com
nameserver xxx.xxx.xxx.xxx (our internal dns)
nameserver xxx.xxx.xxx.xxx (primary external dns)
nameserver xxx.xxx.xxx.xxx (secondary external dns)
Like I said, the box in question can ping anything via name. No one can ping it via name. I know I can add the box to anybodies host file, whether windows or linux and then they could see it, but I would like to understand how named "adds" newly introduced hosts.
thanks again
Hello,
OK. You must edit two files on the dns server: forward resolution file and reverse resolution file (if you have reverse resolution).
Take a look at the configuration file of named /etc/named.conf (bind 8 and later) or /etc/named.boot to see the names of the zone files.
At the forward resolution file for the zone you must add an entry like:
hostname IN A IP_ADDRESS
For example:
shark IN A 192.168.1.33
Save the changes, exit.
For the reverse resolution file, if you use this kind of resolution (from IP to hostname) you have to consider the name of the file too, something like 1.168.192.in-addr.arpa. The name of the file tells that is refering to the reverse resolution of the net 192.168.1 so the entry that you have to include consist only of the last number of the IP address:
33 IN PTR shark.yourdomain.com.
Or something similar.
Then reestart the in.named server to make the changes available.
The best thing is to chech other entries at these files and copy the sintaxis to have the same kind of names.
Consider one thing: THE POINT AT THE END OF AN ADDRESS IS NOT A MISTAKE. IT MEANS THAT THE NAME IS ABSOLUTE, THAT IS, THAT THE NAME shark.yourdomain.com IS COMPLETE. IF YOU SEE THE FORWARD RESOLUTION FILE EXAMPLE ENTRY I'VE POSTED, YOU'LL SEE THAT IT HAS NO POINT, SO THE NAME WILL BE COMPLETED WITH THE DOMAINNAME ASSOCIATED TO THIS FILE.
So the best way if you need a fast solution is to use the information I posted and copy the sintaxis of previous entries at the configuration files. Then, of course, take a look at the available documentation about dns (google).
If you have any question just post again. Good luck,
jmiturbe
OK. You must edit two files on the dns server: forward resolution file and reverse resolution file (if you have reverse resolution).
Take a look at the configuration file of named /etc/named.conf (bind 8 and later) or /etc/named.boot to see the names of the zone files.
At the forward resolution file for the zone you must add an entry like:
hostname IN A IP_ADDRESS
For example:
shark IN A 192.168.1.33
Save the changes, exit.
For the reverse resolution file, if you use this kind of resolution (from IP to hostname) you have to consider the name of the file too, something like 1.168.192.in-addr.arpa. The name of the file tells that is refering to the reverse resolution of the net 192.168.1 so the entry that you have to include consist only of the last number of the IP address:
33 IN PTR shark.yourdomain.com.
Or something similar.
Then reestart the in.named server to make the changes available.
The best thing is to chech other entries at these files and copy the sintaxis to have the same kind of names.
Consider one thing: THE POINT AT THE END OF AN ADDRESS IS NOT A MISTAKE. IT MEANS THAT THE NAME IS ABSOLUTE, THAT IS, THAT THE NAME shark.yourdomain.com IS COMPLETE. IF YOU SEE THE FORWARD RESOLUTION FILE EXAMPLE ENTRY I'VE POSTED, YOU'LL SEE THAT IT HAS NO POINT, SO THE NAME WILL BE COMPLETED WITH THE DOMAINNAME ASSOCIATED TO THIS FILE.
So the best way if you need a fast solution is to use the information I posted and copy the sintaxis of previous entries at the configuration files. Then, of course, take a look at the available documentation about dns (google).
If you have any question just post again. Good luck,
jmiturbe
- Thread starter
- #6
paleogryph
MIS
jmiturbe, that did the trick. Thanks.
I knew about those files and saw that they contained the records of names/addresses in their respective networks. However, I assumed (wrongly) that named somehow "dynamically" added address/name pairings. Also, for some reason they were permed as 444 so I had to !w to save them. Once I restarted named all was well.
I knew about those files and saw that they contained the records of names/addresses in their respective networks. However, I assumed (wrongly) that named somehow "dynamically" added address/name pairings. Also, for some reason they were permed as 444 so I had to !w to save them. Once I restarted named all was well.
- Status
Similar threads