david875
asked on
BIND : Ping Failed when i ping my CentOS Server
when i reboot the server i couldn't ping linux.local
here is my linux.local file config
$TTL 1H
@ IN SOA ns1.linux.local. root (
2009091114 ; serial
1H ; refresh
15M ; retry
4W ; expire
1H ; Negative caching TTL of 1 hour
)
; Name servers
IN NS ns1.linux.local.
ns1 IN A 10.10.10.100
www IN A 10.10.10.100
ftp IN A 10.10.10.100
linux.local IN A 10.10.10.100
Any idea?
screenshot.JPG
here is my linux.local file config
$TTL 1H
@ IN SOA ns1.linux.local. root (
2009091114 ; serial
1H ; refresh
15M ; retry
4W ; expire
1H ; Negative caching TTL of 1 hour
)
; Name servers
IN NS ns1.linux.local.
ns1 IN A 10.10.10.100
www IN A 10.10.10.100
ftp IN A 10.10.10.100
linux.local IN A 10.10.10.100
Any idea?
screenshot.JPG
not in the windows host files? not in the dns serve?!
ASKER
hold on but what you mean, i didn't understand what you said, forgive me
run the following command on your centos box and it will be clear why you have an issue.
dig @localhost axfr linux.local
pay attention to the linux.local (unterminated line)
replace the linux.local with @ or add a period at the end of the linux.local. IN A line and update the serial number to correct the issue.
dig @localhost axfr linux.local
pay attention to the linux.local (unterminated line)
replace the linux.local with @ or add a period at the end of the linux.local. IN A line and update the serial number to correct the issue.
ASKER
It didnt work with what you said, i tried to replace linux.local with an "@" and nthing, i tried also to add a dot "." after linux.local. but nothing, here is what your command gives:
[linux.local named]# dig @localhost axfr linux.local
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1 .el5_5.3 <<>> @localhost axfr linux.local
; (1 server found)
;; global options: printcmd
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
linux.local. 3600 IN NS ns1.linux.local.
ftp.linux.local. 3600 IN A 10.10.10.100
linux.local.linux.local. 3600 IN A 10.10.10.100
ns1.linux.local. 3600 IN A 10.10.10.100
www.linux.local. 3600 IN A 10.10.10.100
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 20 15:35:10 2011
;; XFR size: 7 records (messages 1)
[linux.local named]#
[linux.local named]# dig @localhost axfr linux.local
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1
; (1 server found)
;; global options: printcmd
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
linux.local. 3600 IN NS ns1.linux.local.
ftp.linux.local. 3600 IN A 10.10.10.100
linux.local.linux.local. 3600 IN A 10.10.10.100
ns1.linux.local. 3600 IN A 10.10.10.100
www.linux.local. 3600 IN A 10.10.10.100
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 20 15:35:10 2011
;; XFR size: 7 records (messages 1)
[linux.local named]#
Did you update the serial number? Did you issue rndc reload linux.local (to have bind reload the zone)
ASKER
no i didn't, i don't have rndc in my config files in /var/named
How to do all this?
I just discovered a funny thing, i started the samba server and i can ping linux.local again but i tried 1 thing, i stopped samba and i can still ping, that's strange , in addition i deleted the line that has
linux.local IN A 10.10.10.100 and saved the config, restarted named, then no ping, but now i see that i can ping, this will make me crazy
How to do all this?
I just discovered a funny thing, i started the samba server and i can ping linux.local again but i tried 1 thing, i stopped samba and i can still ping, that's strange , in addition i deleted the line that has
linux.local IN A 10.10.10.100 and saved the config, restarted named, then no ping, but now i see that i can ping, this will make me crazy
Note that your TTL the number between the left most record and the IN directive is 3600. This is how long the record is kept on any one system.
so you ping linux.local that fails the negative response is cached on the system.
You then update the record and reload named. While the server now has a new set of information, the system that has a negative cache will not check with the server until the time runs out.
To setup RNDC you need to run /usr/sbin/rndc-confgen
You then copy the output as directed. one portion into /etc/rndc.cong and one portion into the top of the /etc/named.conf file. You would once again need to restart named /etc/init.d/named restart.
rndc reconfig deals if you are adding a zone and do not want the whole named to restart
rndc reload tells named to reload all information
rndc reload zonename tells named that zonename has changed and it should be reprocessed.
so you ping linux.local that fails the negative response is cached on the system.
You then update the record and reload named. While the server now has a new set of information, the system that has a negative cache will not check with the server until the time runs out.
To setup RNDC you need to run /usr/sbin/rndc-confgen
You then copy the output as directed. one portion into /etc/rndc.cong and one portion into the top of the /etc/named.conf file. You would once again need to restart named /etc/init.d/named restart.
rndc reconfig deals if you are adding a zone and do not want the whole named to restart
rndc reload tells named to reload all information
rndc reload zonename tells named that zonename has changed and it should be reprocessed.
ASKER
thank you for the useful information @arnold, you're doing a great effort with me :)
I configured now rndc and everything is OK
I must tell you something, i'm not experienced with BIND, i'm doing my first experiences with it, you said TTL mustbe 3600? in config all TTL are 3600 so what should i do?
I configured now rndc and everything is OK
I must tell you something, i'm not experienced with BIND, i'm doing my first experiences with it, you said TTL mustbe 3600? in config all TTL are 3600 so what should i do?
It is not an issue of what you should do it was just a statement that your current zone config has the setting for the TTL at 3600 (seconds)
The issue is as follows. if you set the TTL low changes within the zone will propagate quicker.
However, the tradeoff is that your DNS server will see many more requests.
i.e. your TTL is 3600 which means the same system that looks up any record will not lookup the same record for 3600 seconds and this is the maximum length of time this system will have to wait to see an update you make to the same record. At 3600 seconds, the maximum number of queries the server will see from this system for this record is 24.
If you lower the TTL to 90 seconds. When you make a change in the zone, it will take 90 seconds for it to be seen, but your server will see a max of 960 queries from this system for this record.
Usually, a higher TTL is better, but if you are planning on making a change, you should lower the TTL a day before such that when the change is made it propagates at a quicker pace and then you can increase it again to limit the number of queries that are generated against your server.(network traffic that might not be necessary)
The issue is as follows. if you set the TTL low changes within the zone will propagate quicker.
However, the tradeoff is that your DNS server will see many more requests.
i.e. your TTL is 3600 which means the same system that looks up any record will not lookup the same record for 3600 seconds and this is the maximum length of time this system will have to wait to see an update you make to the same record. At 3600 seconds, the maximum number of queries the server will see from this system for this record is 24.
If you lower the TTL to 90 seconds. When you make a change in the zone, it will take 90 seconds for it to be seen, but your server will see a max of 960 queries from this system for this record.
Usually, a higher TTL is better, but if you are planning on making a change, you should lower the TTL a day before such that when the change is made it propagates at a quicker pace and then you can increase it again to limit the number of queries that are generated against your server.(network traffic that might not be necessary)
ASKER
ok so this is why the ping fail against linux.local? the strange thing is that i can ping ns1.linux.local or www.linux.local from the first time without any problem
ASKER
and i think that the Negative caching TTL of 1 hour is much time, maybe i should lower it to 90 seconds as you said, what do you think?
ASKER
just to understand 1 thing and sorry to post many questions because they come time after time, if i can't ping linux.local the system will wait 1 H to update and see that ping again?
The negative caching only deals with a record that could not be looked up.
could you post the new info
dig @localhost axfr linux.local
as well as the contents of the linux.local zone.
could you post the new info
dig @localhost axfr linux.local
as well as the contents of the linux.local zone.
ASKER
[linux.local ~]# dig @localhost axfr linux.local
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1 .el5_5.3 <<>> @localhost axfr linux.local
; (1 server found)
;; global options: printcmd
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
linux.local. 3600 IN NS ns1.linux.local.
ftp.linux.local. 3600 IN A 10.10.10.100
ns1.linux.local. 3600 IN A 10.10.10.100
www.linux.local. 3600 IN A 10.10.10.100
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 20 18:06:30 2011
;; XFR size: 6 records (messages 1)
[linux.local ~]#nano /var/named/linux.local
$TTL 1H
@ IN SOA ns1.linux.local. root (
2009091114 ; serial
1H ; refresh
15M ; retry
4W ; expire
1H ; Negative caching TTL of 1 hour
)
; Name servers
IN NS ns1.linux.local.
ns1 IN A 10.10.10.100
www IN A 10.10.10.100
ftp IN A 10.10.10.100
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1
; (1 server found)
;; global options: printcmd
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
linux.local. 3600 IN NS ns1.linux.local.
ftp.linux.local. 3600 IN A 10.10.10.100
ns1.linux.local. 3600 IN A 10.10.10.100
www.linux.local. 3600 IN A 10.10.10.100
linux.local. 3600 IN SOA ns1.linux.local. root.linux.local. 2009091114 3600 900 2419200 3600
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 20 18:06:30 2011
;; XFR size: 6 records (messages 1)
[linux.local ~]#nano /var/named/linux.local
$TTL 1H
@ IN SOA ns1.linux.local. root (
2009091114 ; serial
1H ; refresh
15M ; retry
4W ; expire
1H ; Negative caching TTL of 1 hour
)
; Name servers
IN NS ns1.linux.local.
ns1 IN A 10.10.10.100
www IN A 10.10.10.100
ftp IN A 10.10.10.100
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
you're the best